From: Bill Davidsen <davidsen@tmr.com>
To: Rik van Riel <riel@redhat.com>
Cc: Nick Piggin <piggin@cyberone.com.au>,
Andrew Morton <akpm@osdl.org>, Andrea Arcangeli <andrea@suse.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: VM patches (please review)
Date: Wed, 04 Feb 2004 18:55:05 -0500 [thread overview]
Message-ID: <40218659.7090605@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402041239311.24515-100000@chimarrao.boston.redhat.com>
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 <davidsen@tmr.com>
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: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2004-02-04 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 3:24 Nick Piggin
2004-02-04 17:16 ` Bill Davidsen
2004-02-04 17:40 ` Rik van Riel
2004-02-04 23:55 ` Bill Davidsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40218659.7090605@tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@osdl.org \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=piggin@cyberone.com.au \
--cc=riel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox