From mboxrd@z Thu Jan 1 00:00:00 1970 From: Topi Miettinen Subject: Re: [PATCH 00/14] Present useful limits to user (v2) Date: Fri, 15 Jul 2016 13:52:48 +0000 Message-ID: <28b4b919-4f50-d9f6-c5e1-d1e92ea1ba1c@gmail.com> References: <1468578983-28229-1-git-send-email-toiwoton@gmail.com> <20160715124330.GR30154@twins.programming.kicks-ass.net> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:openpgp:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=CHtbySHLYUC5CFdguDeaZTLDXV7X6U6tT0qW3eMNc9E=; b=Ms64TjbKo95W45DmsSqkfwQSimaZ5Reo0cFODSMUcH2a2e35YamDmOMphJi0dL0r5K hTUrbQ3ljFFKBA8D4O7qwawNvE69PoGGTtr0gOM7STY9mp2k2RSEDaabz7FXjPp20fYz C+jFMpdiKWsmaJvEXDGjzJTaF23uTj9+siQmuwXreTYDV2YtOOOpdhlK3WnXO2d4eNPa jKQwZI8gN+8SUbqKVonduL/0ChlxqO48SQ6a+VS8FPf6cNsqH6CGv12XRkAA9P12mHpE QJc8ko2HydTNdRDpSMWFLRsZ8h5m+Qma0D75d1vXbvuZZ2yuqfmU9DJMvr1WaquIyZu4 OmOQ== In-Reply-To: <20160715124330.GR30154@twins.programming.kicks-ass.net> Sender: owner-linux-mm@kvack.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Peter Zijlstra Cc: linux-kernel@vger.kernel.org, Jonathan Corbet , Tony Luck , Fenghua Yu , Alexander Graf , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , Doug Ledford , Sean Hefty , Hal Rosenstock , Mike Marciniszyn , Dennis Dalessandro , Christian Benvenuti , Dave Goodell , Sudeep Dutt , Ashu 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? -Topi -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org