From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm <linux-mm@kvack.org>, Linus Torvalds <torvalds@osdl.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: inactive-clean list
Date: Tue, 18 Jul 2006 14:16:35 +0200 [thread overview]
Message-ID: <1153224998.2041.15.camel@lappy> (raw)
In-Reply-To: <Pine.LNX.4.64.0607172035140.28956@schroedinger.engr.sgi.com>
On Mon, 2006-07-17 at 20:37 -0700, Christoph Lameter wrote:
> On Mon, 17 Jul 2006, Peter Zijlstra wrote:
>
> > This patch implements the inactive_clean list spoken of during the VM summit.
> > The LRU tail pages will be unmapped and ready to free, but not freeed.
> > This gives reclaim an extra chance.
>
> I thought we wanted to just track the number of unmapped clean pages and
> insure that they do not go under a certain limit? That would not require
> any locking changes but just a new zoned counter and a check in the dirty
> handling path.
The problem I see with that is that we cannot create new unmapped clean
pages. Where will we get new pages to satisfy our demand when there is
nothing mmap'ed.
This approach will generate them by forceing some pages into swap space.
--
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>
next prev parent reply other threads:[~2006-07-18 12:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 20:24 Peter Zijlstra
2006-07-18 3:37 ` Christoph Lameter
2006-07-18 12:16 ` Peter Zijlstra [this message]
2006-07-18 13:29 ` Christoph Lameter
2006-07-18 13:55 ` Martin J. Bligh
2006-07-18 13:59 ` Christoph Lameter
2006-07-18 15:12 ` Martin J. Bligh
2006-07-18 15:57 ` Christoph Lameter
2006-07-18 16:23 ` Martin J. Bligh
2006-07-18 14:03 ` Christoph Lameter
2006-07-18 14:25 ` Andrew Morton
2006-07-18 14:45 ` Christoph Lameter
2006-07-18 15:59 ` KAMEZAWA Hiroyuki
2006-07-23 5:50 ` Rik van Riel
2006-07-24 18:11 ` Christoph Lameter
2006-07-24 19:00 ` Rik van Riel
2006-07-25 20:25 ` Christoph Lameter
2006-07-25 21:37 ` Rik van Riel
2006-07-25 23:03 ` Christoph Lameter
2006-07-26 0:02 ` Rik van Riel
2006-07-26 0:05 ` Christoph Lameter
2006-07-26 11:00 ` Martin Schwidefsky
2006-07-26 11:11 ` Peter Zijlstra
2006-07-26 13:04 ` Martin Schwidefsky
2006-07-26 14:45 ` Peter Zijlstra
2006-07-27 11:16 ` Martin Schwidefsky
2006-07-26 15:41 ` Rik van Riel
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=1153224998.2041.15.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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