All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Hugh Dickins <hugh@veritas.com>, linux-mm@kvack.org
Subject: Re: Drop PageReclaim()
Date: Thu, 8 Feb 2007 15:13:41 -0800	[thread overview]
Message-ID: <20070208151341.7e27ca59.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702081438510.15063@schroedinger.engr.sgi.com>

On Thu, 8 Feb 2007 14:40:52 -0800 (PST)
Christoph Lameter <clameter@sgi.com> wrote:

> On Thu, 8 Feb 2007, Andrew Morton wrote:
> 
> > > Those sleeping on the page must have their own process context
> > > to do so.
> > 
> > You've lost me.  I don't see what that sort of thing has to do with
> > end_page_writeback() and rotate_reclaimable_page().
> 
> One could replace the PageReclaim bit with a process waiting on the 
> writeback bit to clear. The process would then do the rotation. But that 
> would require too many processes.

Yeah, we'd need to queue the pages somehow to do that.

> Hmmm... Does not look as if I can get that bit freed up. It was always a 
> mystery to me what the thing did. At least I know now.

well hmm.  Maybe we can just remove PG_reclaim.

The current situation is that we'll rotate a written-back page to the tail
of the inactive list if

	a) the page looks like it'll be reclaimable and
	b) the vm scanner recently encountered that page and wanted to
	   reclaim it.

if we remove PG_reclaim then condition b) just goes away.

I expect that'll be OK for pages which were written back by the vm scanner.
 But it also means that pages which were written back by
pdflush/balance_dirty_pages/fsync/etc will now all also be eligible for
rotation.  ie: the vast majority of written-back pages.

Whether that will make much difference to page aging I don't know.  But it
will cause more lru->lock traffic.

--
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:[~2007-02-08 23:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 14:13 Drop PageReclaim() Christoph Lameter
2007-02-07 14:32 ` Hugh Dickins
2007-02-08 21:20   ` Christoph Lameter
2007-02-08 21:38     ` Christoph Lameter
2007-02-08 21:42       ` Christoph Lameter
2007-02-08 21:55         ` Christoph Lameter
2007-02-08 22:03           ` Andrew Morton
2007-02-08 22:14             ` Christoph Lameter
2007-02-08 22:24               ` Andrew Morton
2007-02-08 22:26                 ` Christoph Lameter
2007-02-08 22:37                   ` Andrew Morton
2007-02-08 22:40                     ` Christoph Lameter
2007-02-08 23:13                       ` Andrew Morton [this message]
2007-02-09  0:22                         ` Christoph Lameter
2007-02-09  0:39                           ` Andrew Morton
2007-02-09  1:06                             ` Christoph Lameter
2007-02-09  1:18                               ` Andrew Morton
2007-02-11  5:12                             ` Rik van Riel
2007-02-07 17:25 ` Andrew Morton
2007-02-08 21:19   ` 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=20070208151341.7e27ca59.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.