From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <40218659.7090605@tmr.com> Date: Wed, 04 Feb 2004 18:55:05 -0500 From: Bill Davidsen MIME-Version: 1.0 Subject: Re: VM patches (please review) References: <402128D0.2020509@tmr.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Rik van Riel Cc: Nick Piggin , Andrew Morton , Andrea Arcangeli , linux-kernel , linux-mm@kvack.org List-ID: Rik van Riel wrote: > On Wed, 4 Feb 2004, Bill Davidsen wrote: > > >>Since this is broken down nicely, a line or two about what each patch >>does or doesn't address would be useful. In particular, having just >>gotten a working RSS I'm suspicious of the patch named vm-no-rss-limit >>being desirable ;-) > > > The bug with the RSS limit patch is that I forgot to > change the exec() code, so when init is exec()d it > gets an RSS limit of zero, which is inherited by all > its children --> always over the RSS limit, no page > aging, etc. > > I need to find the cleanest way to add the inheriting > of RSS limit at exec time and send a patchlet for that > to akpm... Thank you! I had assumed that the info was being carried through exec, fork, and pthread_* and similar, and just not enforced. I still think this will be great for those applications known to occasionally get a tough data set and not converge or recurse beyond all sense. -- bill davidsen CTO TMR Associates, Inc Doing interesting things with small computers since 1979 -- 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: aart@kvack.org