From: Rik van Riel <riel@redhat.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
Nick Piggin <nickpiggin@yahoo.com.au>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
"Martin J. Bligh" <mbligh@mbligh.org>
Subject: Re: [RFC] Remove unswappable anonymous pages off the LRU
Date: Thu, 15 Feb 2007 17:31:04 -0500 [thread overview]
Message-ID: <45D4DF28.7070409@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702151300500.31366@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> If we do not have any swap or we have run out of swap then anonymous pages
> can no longer be removed from memory. In that case we simply treat them
> like mlocked pages.
Running out of swap is a temporary condition.
You need to have some way for those pages to
make it back onto the LRU list when swap
becomes available.
Better yet, we could implement a better way to
reclaim swap space, or reclaim swap space in a
different part of the code.
For example, we could try to reclaim the swap
space of every page that we scan on the active
list - when swap space starts getting tight.
--
All Rights Reversed
--
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:[~2007-02-15 22:31 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 21:05 [RFC] Remove unswappable anonymous pages off the LRU Christoph Lameter
2007-02-15 22:31 ` Rik van Riel [this message]
2007-02-15 22:41 ` Christoph Lameter
2007-02-15 22:50 ` Rik van Riel
2007-02-15 22:53 ` Christoph Lameter
2007-02-15 23:19 ` Andrew Morton
2007-02-15 23:20 ` Lee Schermerhorn
2007-02-16 0:15 ` Andrew Morton
2007-02-16 1:13 ` Andrew Morton
2007-02-16 1:24 ` KAMEZAWA Hiroyuki
2007-02-16 1:40 ` Martin Bligh
2007-02-16 1:49 ` Andrew Morton
2007-02-16 2:21 ` Martin Bligh
2007-02-16 2:34 ` Christoph Lameter
2007-02-16 2:48 ` Andrew Morton
2007-02-16 2:50 ` Christoph Lameter
2007-02-16 3:18 ` Andrew Morton
2007-02-16 3:36 ` Christoph Lameter
2007-02-16 3:42 ` Andrew Morton
2007-02-16 3:50 ` Christoph Lameter
2007-02-16 4:02 ` Andrew Morton
2007-02-16 4:07 ` Christoph Lameter
2007-02-16 4:03 ` Andrew Morton
2007-02-16 4:14 ` Rik van Riel
2007-02-16 4:15 ` Christoph Lameter
2007-02-16 4:57 ` KAMEZAWA Hiroyuki
2007-02-16 5:16 ` Andrew Morton
2007-02-16 5:25 ` Christoph Lameter
2007-02-16 5:41 ` Andrew Morton
2007-02-16 5:19 ` Christoph Lameter
2007-02-16 4:24 ` Andrew Morton
2007-02-16 8:15 ` Peter Zijlstra
2007-02-16 9:11 ` Rafael J. Wysocki
2007-02-16 9:19 ` Peter Zijlstra
2007-02-16 10:10 ` Christoph Lameter
2007-02-16 10:17 ` Peter Zijlstra
2007-02-16 11:04 ` Rafael J. Wysocki
2007-02-16 2:16 ` Christoph Lameter
2007-02-16 3:17 ` Martin Bligh
2007-02-16 3:29 ` Christoph Lameter
2007-02-16 8:10 ` Peter Zijlstra
2007-02-16 2:15 ` Christoph Lameter
2007-02-16 2:55 ` Christoph Lameter
2007-02-16 5:02 ` 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=45D4DF28.7070409@redhat.com \
--to=riel@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.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;
as well as URLs for NNTP newsgroup(s).