From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH 00/14] Present useful limits to user (v2) Date: Fri, 15 Jul 2016 13:54:44 -0700 Message-ID: <201607152054.u6FKslD1005327__48771.5345960625$1468618896$gmane$org@mail.zytor.com> References: <1468578983-28229-1-git-send-email-toiwoton@gmail.com> <20160715124330.GR30154@twins.programming.kicks-ass.net> <28b4b919-4f50-d9f6-c5e1-d1e92ea1ba1c@gmail.com> <20160715135956.GA3115@twins.programming.kicks-ass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: linux-kernel@vger.kernel.org, Jonathan Corbet , Tony Luck , Fenghua Yu , Alexander Graf , Paolo Bonzini , Radim Kr??m???? , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , Thomas Gleixner , Ingo Molnar , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , Doug Ledford , Sean Hefty , Hal Rosenstock , Mike Marciniszyn , Dennis Dalessandro , Christian Benvenuti , Dave Goodell , Sudeep Dutt , Ashutosh Dixit , Alex W To: Peter Zijlstra , Topi Miettinen Return-path: Received: from terminus.zytor.com ([198.137.202.10]:42418 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751630AbcGOVE1 (ORCPT ); Fri, 15 Jul 2016 17:04:27 -0400 In-Reply-To: <20160715135956.GA3115@twins.programming.kicks-ass.net> Sender: kvm-owner@vger.kernel.org List-ID: ,Johannes Weiner ,Alexei Starovoitov ,Arnaldo Carvalho de Melo ,Alexander Shishkin ,Balbir Singh ,Markus Elfring ,"David S. Miller" ,Nicolas Dichtel ,Andrew Morton ,Konstantin Khlebnikov ,Jiri Slaby ,Cyrill Gorcunov ,Michal Hocko ,Vlastimil Babka ,Dave Hansen ,Greg Kroah-Hartman ,Dan Carpenter ,Michael Kerrisk ,"Kirill A. Shutemov" ,Marcus Gelderie ,Vladimir Davydov ,Joe Perches ,Frederic Weisbecker ,Andrea Arcangeli ,! "Eric W. Biederman" ,Andi Kleen ,Oleg Nesterov ,Stas Sergeev ,Amanieu d'Antras ,Richard Weinberger ,Wang Xiaoqiang ,Helge Deller ,Mateusz Guzik ,Alex Thorlton ,Ben Segall ,John Stultz ,Rik van Riel ,Eric B Munson ,Alexey Klimov ,Chen Gang ,Andrey Ryabinin ,David Rientjes ,Hugh Dickins ,Alexander Kuleshov ,"open list:DOCUMENTATION" ,"open list:IA64 (Itanium) PLATFORM" ,"open list:KERNEL VIRTUAL MACHINE (KVM) FOR POWERPC" ,"open list:KERNEL VIRTUAL MACHINE (KVM)" ,"open list:LINUX FOR POWERPC! (32-BIT AND 64-BIT)" ,"open list:INFINIBAND SUBSYSTEM" ,"open list:FILESYSTEMS (VFS and infrastructure)" ,"open list:CONTROL GROUP (CGROUP)" ,"open list:BPF (Safe dynamic programs and tools)" ,"open list:MEMORY MANAGEMENT" Message-ID: On July 15, 2016 6:59:56 AM PDT, Peter Zijlstra 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.