From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx134.postini.com [74.125.245.134]) by kanga.kvack.org (Postfix) with SMTP id 5AD1F90001B for ; Thu, 13 Jun 2013 12:13:24 -0400 (EDT) Date: Thu, 13 Jun 2013 10:43:47 -0400 From: =?utf-8?B?SsO2cm4=?= Engel Subject: Re: [PATCH, RFC] mm: Implement RLIMIT_RSS Message-ID: <20130613144347.GA13217@logfs.org> References: <20130611182921.GB25941@logfs.org> <20130611211601.GA29426@cmpxchg.org> <20130611215319.GA29368@logfs.org> <20130613085732.GB4533@bbox> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20130613085732.GB4533@bbox> Sender: owner-linux-mm@kvack.org List-ID: To: Minchan Kim Cc: Johannes Weiner , linux-mm@kvack.org, linux-kernel@vger.kernel.org On Thu, 13 June 2013 17:57:32 +0900, Minchan Kim wrote: > > It means you already know the max rss of the application in advance > so you can use taskstats's hiwater_rss if you don't need to catch > the moment which rss is over the limit. I would like to catch the very moment. Just for my particular needs, it doesn't matter much if you overshoot by 10% or so. But eventually I would like a patch that is off by less than 1% and low-overhead at the same time. JA?rn -- Measuring programming progress by lines of code is like measuring aircraft building progress by weight. -- Bill Gates -- 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