From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 11 Oct 2006 18:36:34 -0400 From: Benjamin LaHaise Subject: Re: RSS accounting (was: Re: 2.6.19-rc1-mm1) Message-ID: <20061011223634.GB18665@kvack.org> References: <1160574913.3000.378.camel@laptopd505.fenrus.org> <000101c6ed58$e01d2830$1680030a@amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000101c6ed58$e01d2830$1680030a@amr.corp.intel.com> Sender: owner-linux-mm@kvack.org Return-Path: To: "Chen, Kenneth W" Cc: 'Arjan van de Ven' , "Eric W. Biederman" , Peter Zijlstra , Andrew Morton , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Nick Piggin List-ID: On Wed, Oct 11, 2006 at 10:15:39AM -0700, Chen, Kenneth W wrote: > 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. If that is the case, it would make sense to account such things as page tables and other kernel allocations against the RSS, which would be useful. That said, it's possible to keep semantics fairly close to those currently implemented by tracking RSS differently for shared vs private areas -- those vmas which are shared could be placed on a list and then summed when RSS is read. That said, I'm not sure it is a good idea, as the cost of obtaining RSS for tools like top is exactly why we have the current counters maintained to provide O(1) semantics. All of the old semantics are covered by smaps, though, so I'd agree with any changes to make RSS reflect allocations incurred by this process. -ben -- "Time is of no importance, Mr. President, only life is important." Don't Email: . -- 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