linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Rik van Riel <riel@redhat.com>,
	Linus Torvalds <torvalds@osdl.org>, Andi Kleen <ak@suse.de>,
	Rohit Seth <rohitseth@google.com>, Andrew Morton <akpm@osdl.org>,
	mbligh@google.com, hugh@veritas.com, andrea@suse.de,
	arjan@infradead.org, apw@shadowen.org, mel@csn.ul.ie,
	marcelo@kvack.org, anton@samba.org, paulmck@us.ibm.com,
	Nick Piggin <piggin@cyberone.com.au>,
	linux-mm <linux-mm@kvack.org>,
	Nikita Danilov <nikita@clusterfs.com>
Subject: Re: [RFC][PATCH] inactive_clean
Date: Mon, 19 Jun 2006 14:48:33 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0606191442450.4739@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1150749971.28517.122.camel@lappy>

On Mon, 19 Jun 2006, Peter Zijlstra wrote:

> You need to increase nr_clean_anon to reach nr_wanted_clean.

nr_clean_anon? Anonymous pages are always dirty! They may appear to be 
clean for a process but fundamentally a clean anonymous page is full of 
zeros. We use a special page for that.

> But you need slightly more than just writeout, you need to create a
> clean anonymous page, so you need to keep it around.

Still boogling on the clean anonymous pages. Maybe with swap you can get
there. You mean the anonymous page is clean when it was written to swap? 
We are dealing with a special case here when the performance already 
sucks and now we add more logic to make the case when performance was not 
bad worse?

If an anonymus page gains a reference to swap then it is fundamentally no 
longer a pure anonymous page.

> LRU page order, and having a preference for file-backed pages breaks it.

zone_reclaim already does not observe that order but goes for the easily 
reclaimable unmapped pages.

--
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>

  reply	other threads:[~2006-06-19 21:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 12:20 Peter Zijlstra
2006-06-19 15:45 ` Christoph Lameter
2006-06-19 18:10   ` Peter Zijlstra
2006-06-19 19:03     ` Christoph Lameter
2006-06-19 19:10       ` Rik van Riel
2006-06-19 19:24         ` Christoph Lameter
2006-06-19 19:27           ` Rik van Riel
2006-06-19 19:58             ` Christoph Lameter
2006-06-19 20:05               ` Peter Zijlstra
2006-06-19 20:11                 ` Christoph Lameter
2006-06-19 20:46                   ` Peter Zijlstra
2006-06-19 21:48                     ` Christoph Lameter [this message]
2006-06-19 20:28               ` Rik van Riel
2006-06-19 21:45                 ` Christoph Lameter

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=Pine.LNX.4.64.0606191442450.4739@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=anton@samba.org \
    --cc=apw@shadowen.org \
    --cc=arjan@infradead.org \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@kvack.org \
    --cc=mbligh@google.com \
    --cc=mel@csn.ul.ie \
    --cc=nikita@clusterfs.com \
    --cc=paulmck@us.ibm.com \
    --cc=piggin@cyberone.com.au \
    --cc=riel@redhat.com \
    --cc=rohitseth@google.com \
    --cc=torvalds@osdl.org \
    /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