From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Chen, Kenneth W" Subject: RE: RSS accounting (was: Re: 2.6.19-rc1-mm1) Date: Wed, 11 Oct 2006 10:15:39 -0700 Message-ID: <000101c6ed58$e01d2830$1680030a@amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <1160574913.3000.378.camel@laptopd505.fenrus.org> Sender: owner-linux-mm@kvack.org Return-Path: To: 'Arjan van de Ven' , "Eric W. Biederman" Cc: Peter Zijlstra , Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Nick Piggin List-ID: Arjan van de Ven wrote on Wednesday, October 11, 2006 6:55 AM > > Well I tried to defined it in terms of what you can use it for. > > > > I would define the resident set size as the total number of bytes > > of physical RAM that a process (or set of processes) is using, > > irrespective of the rest of the system. > > > > So I think the counting should be primarily about what is mapped into > > the page tables. But other things can be added as is appropriate or > > easy. > > > > The practical effect should be that an application that needs more > > pages than it's specified RSS to avoid thrashing should thrash but > > it shouldn't take the rest of the system with it. > > > so by your definition, hugepages are part of RSS. > > Ken: what is your definition of RSS ? I'm more inclined to define RSS as "how much ram does my application cause to be used". To monitor process's working set size, We already have /proc//smaps. Whether we can use working set size in an intelligent way in mm is an interesting question. Though, so far such accounting is not utilized at all. - Ken -- 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