<[email protected]>,Johannes Weiner <[email protected]>,Alexei Starovoitov <[email protected]>,Arnaldo Carvalho de Melo <[email protected]>,Alexander Shishkin <[email protected]>,Balbir Singh <[email protected]>,Markus Elfring <[email protected]>,"David S. Miller" <[email protected]>,Nicolas Dichtel <[email protected]>,Andrew Morton <[email protected]>,Konstantin Khlebnikov <[email protected]>,Jiri Slaby <[email protected]>,Cyrill Gorcunov <[email protected]>,Michal Hocko <[email protected]>,Vlastimil Babka <[email protected]>,Dave Hansen <[email protected]>,Greg Kroah-Hartman <[email protected]>,Dan Carpenter <[email protected]>,Michael Kerrisk <[email protected]>,"Kirill A. Shutemov" <[email protected]>,Marcus Gelderie <[email protected]>,Vladimir Davydov <[email protected]>,Joe Perches <[email protected]>,Frederic Weisbecker <[email protected]>,Andrea Arcangeli <[email protected]>,! "Eric W. Biederman" <[email protected]>,Andi Kleen <[email protected]>,Oleg Nesterov <[email protected]>,Stas Sergeev <[email protected]>,Amanieu d'Antras <[email protected]>,Richard Weinberger <[email protected]>,Wang Xiaoqiang <[email protected]>,Helge Deller <[email protected]>,Mateusz Guzik <[email protected]>,Alex Thorlton <[email protected]>,Ben Segall <[email protected]>,John Stultz <[email protected]>,Rik van Riel <[email protected]>,Eric B Munson <[email protected]>,Alexey Klimov <[email protected]>,Chen Gang <[email protected]>,Andrey Ryabinin <[email protected]>,David Rientjes <[email protected]>,Hugh Dickins <[email protected]>,Alexander Kuleshov <[email protected]>,"open list:DOCUMENTATION" <[email protected]>,"open list:IA64 (Itanium) PLATFORM" <[email protected]>,"open list:KERNEL VIRTUAL MACHINE (KVM) FOR POWERPC" <[email protected]>,"open list:KERNEL VIRTUAL MACHINE (KVM)" <[email protected]>,"open list:LINUX FOR POWERPC! (32-BIT AND 64-BIT)" <[email protected]>,"open list:INFINIBAND SUBSYSTEM" <[email protected]>,"open list:FILESYSTEMS (VFS and infrastructure)" <[email protected]>,"open list:CONTROL GROUP (CGROUP)" <[email protected]>,"open list:BPF (Safe dynamic programs and tools)" <[email protected]>,"open list:MEMORY MANAGEMENT" <[email protected]> Message-ID: <[email protected]>
On July 15, 2016 6:59:56 AM PDT, Peter Zijlstra <[email protected]> wrote: >On Fri, Jul 15, 2016 at 01:52:48PM +0000, Topi Miettinen wrote: >> On 07/15/16 12:43, Peter Zijlstra wrote: >> > On Fri, Jul 15, 2016 at 01:35:47PM +0300, Topi Miettinen wrote: >> >> Hello, >> >> >> >> There are many basic ways to control processes, including >capabilities, >> >> cgroups and resource limits. However, there are far fewer ways to >find out >> >> useful values for the limits, except blind trial and error. >> >> >> >> This patch series attempts to fix that by giving at least a nice >starting >> >> point from the highwater mark values of the resources in question. >> >> I looked where each limit is checked and added a call to update >the mark >> >> nearby. >> > >> > And how is that useful? Setting things to the high watermark is >> > basically the same as not setting the limit at all. >> >> What else would you use, too small limits? > >That question doesn't make sense. > >What's the point of setting a limit if it ends up being the same as >no-limit (aka unlimited). > >If you cannot explain; and you have not so far; what use these values >are, why would we look at the patches. One reason is to catch a malfunctioning process rather than dragging the whole system down with it. It could also be useful for development. -- Sent from my Android device with K-9 Mail. Please excuse brevity and formatting. -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
