From: Peter Zijlstra <peter@programming.kicks-ass.net>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Coywolf Qi Hunt <coywolf@gmail.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org,
christoph@lameter.com
Subject: Re: + vmscan-rename-functions.patch added to -mm tree
Date: Wed, 15 Feb 2006 12:59:00 +0100 [thread overview]
Message-ID: <1140004740.6087.83.camel@localhost.localdomain> (raw)
In-Reply-To: <43F2E7C8.9040600@yahoo.com.au>
On Wed, 2006-02-15 at 19:35 +1100, Nick Piggin wrote:
> Peter Zijlstra wrote:
> > On Wed, 2006-02-15 at 14:09 +1100, Nick Piggin wrote:
>
> >>shrink_zone and do_shrink_zone don't really say any more to me than
> >>shrink_zone and shrink_cache.
> >
> >
> > I know not everybody believes in a plugable reclaim policy, but that is
> > what I'm building. And from that POV I'd rather not see the
> > active/inactive names get used here.
> >
>
> active/inactive is what we have now. If you manage to get a pluggable
> reclaim policy merged then I assure you, renaming these yet again will
> be the least of your worries :)
True indeed.
> > My vote goes to Coywolf's suggestion.
> >
>
> What was that?
Hmm, seems like I shouldn't read email before waking up, apparently I
got the quoting levels mixed up.
Anyway, this one:
>> try_to_free_pages
>> ->shrink_zones(struct zone **zones, ..)
>> ->shrink_zone(struct zone *, ...)
>> ->do_shrink_zone(struct zone *, ...)
>> ->shrink_page_list(struct list_head *, ...)
prev parent reply other threads:[~2006-02-15 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200602120605.k1C65QFE028051@shell0.pdx.osdl.net>
2006-02-15 2:47 ` + vmscan-rename-functions.patch added to -mm tree Coywolf Qi Hunt
2006-02-15 3:09 ` Nick Piggin
2006-02-15 6:46 ` Peter Zijlstra
2006-02-15 8:35 ` Nick Piggin
2006-02-15 11:59 ` Peter Zijlstra [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=1140004740.6087.83.camel@localhost.localdomain \
--to=peter@programming.kicks-ass.net \
--cc=akpm@osdl.org \
--cc=christoph@lameter.com \
--cc=coywolf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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