From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@ucw.cz>, LKML <linux-kernel@vger.kernel.org>,
Nigel Cunningham <ncunningham@linuxmail.org>,
Johannes Berg <johannes@sipsolutions.net>,
Christoph Lameter <clameter@sgi.com>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: [RFC][PATCH 0/3] swsusp: Stop using page flags
Date: Sun, 11 Mar 2007 11:52:05 +0100 [thread overview]
Message-ID: <1173610325.5182.1.camel@lappy> (raw)
In-Reply-To: <200703111117.27083.rjw@sisk.pl>
On Sun, 2007-03-11 at 11:17 +0100, Rafael J. Wysocki wrote:
> Hi,
>
> The following three patches make swsusp use its own data structures for memory
> management instead of special page flags. Thus the page flags used so far by
> swsusp (PG_nosave, PG_nosave_free) can be used for other purposes and I believe
> there are some urgend needs of them. :-)
>
> Last week I sent these patches to the linux-pm and linux-mm lists and there
> were no negative comments. Also I've been testing them on my x86_64 boxes for
> a few days and apparently they don't break anything. I think they can go into
> -mm for testing.
>
> Comments are welcome.
These patches have my blessing, they look good to me, but I'm not much
involved with the swsusp code, so I won't ACK them.
Again, thanks a bunch for freeing up 2 page flags :-)
Peter
prev parent reply other threads:[~2007-03-11 10:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 10:17 [RFC][PATCH 0/3] swsusp: Stop using page flags Rafael J. Wysocki
2007-03-11 10:26 ` [RFC][PATCH 1/3] swsusp: Use inline functions for changing " Rafael J. Wysocki
2007-03-12 9:01 ` Pavel Machek
2007-03-11 10:31 ` [RFC][PATCH 2/3] swsusp: Do not use " Rafael J. Wysocki
2007-03-12 9:03 ` Pavel Machek
2007-03-11 10:34 ` [RFC][PATCH 3/3] mm: Remove unused " Rafael J. Wysocki
2007-03-12 9:03 ` Pavel Machek
2007-03-11 10:52 ` Peter Zijlstra [this message]
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=1173610325.5182.1.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=clameter@sgi.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.org \
--cc=nickpiggin@yahoo.com.au \
--cc=pavel@ucw.cz \
--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