From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Christoph Lameter <clameter@engr.sgi.com>,
Peter Zijlstra <peter@programming.kicks-ass.net>
Cc: Andrew Morton <akpm@osdl.org>,
linux-mm@kvack.org, nickpiggin@yahoo.com.au,
Bob Picco <bob.picco@hp.com>
Subject: pluggable reclaim infrastructure
Date: Thu, 16 Feb 2006 09:01:51 -0600 [thread overview]
Message-ID: <20060216150151.GA24842@dmt.cnet> (raw)
In-Reply-To: <Pine.LNX.4.62.0602111424050.24990@schroedinger.engr.sgi.com>
Hi,
On Sat, Feb 11, 2006 at 02:25:57PM -0800, Christoph Lameter wrote:
> Here is a new rev of the earlier patch that moves the determination of
> reclaim_mapped into shrink_zone(). This means that refill_inactive does
> not depend on scan control anymore. And its properly formatted for 80
> columns
Can we please hold off this reclaim tweaks for a while? Peter's
pluggable page-replace infrastructure does more fundamental and
important changes to the reclaim code (along with better organization
and separation of the heuristics such as reclaim_mapped, etc.), and
having vmscan.c to change often (as it is now) is just a pain in the
arse to handle.
Its not going to take long for the patchset to be sent for
review/shaping.
--
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:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2006-02-16 15:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 21:39 Skip reclaim_mapped determination if we do not swap Christoph Lameter
2006-02-11 21:50 ` Andrew Morton
2006-02-11 22:10 ` Christoph Lameter
2006-02-11 23:29 ` Andrew Morton
2006-02-12 0:59 ` Christoph Lameter
2006-02-11 22:25 ` Christoph Lameter
2006-02-16 15:01 ` Marcelo Tosatti [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=20060216150151.GA24842@dmt.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=akpm@osdl.org \
--cc=bob.picco@hp.com \
--cc=clameter@engr.sgi.com \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=peter@programming.kicks-ass.net \
/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