From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <clameter@sgi.com>,
Martin Bligh <mbligh@mbligh.org>,
linux-mm@kvack.org, Nick Piggin <nickpiggin@yahoo.com.au>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>
Subject: Re: [RFC] Remove unswappable anonymous pages off the LRU
Date: Fri, 16 Feb 2007 10:19:11 +0100 [thread overview]
Message-ID: <1171617551.24923.56.camel@twins> (raw)
In-Reply-To: <200702161011.40640.rjw@sisk.pl>
On Fri, 2007-02-16 at 10:11 +0100, Rafael J. Wysocki wrote:
> On Friday, 16 February 2007 09:15, Peter Zijlstra wrote:
> > On Thu, 2007-02-15 at 18:48 -0800, Andrew Morton wrote:
> >
> > > The two swsusp bits can be removed: they're only needed at suspend/resume
> > > time and can be replaced by an external data structure.
> >
> > I once had a talk with Rafael, and he said it would be possible to rid
> > us of PG_nosave* with the now not so new bitmap code that is used to
> > handle swsusp of highmem pages.
>
> Yes, that is true.
>
> I'm going to do this soon,
Great!
> but first I'd like to help to make the task freezer
> suitable for the CPU hotplug.
A worthy challenge, have fun :-)
--
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-16 9:19 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
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 [this message]
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=1171617551.24923.56.camel@twins \
--to=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 \
--cc=riel@redhat.com \
--cc=rjw@sisk.pl \
/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).