From: Nigel Cunningham <ncunningham@cyclades.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Pavel Machek <pavel@ucw.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Free swap suspend from dependency on PageReserved
Date: Fri, 07 Oct 2005 15:33:25 +1000 [thread overview]
Message-ID: <1128663205.13507.23.camel@localhost> (raw)
In-Reply-To: <4344F90C.9070001@yahoo.com.au>
Hi Nick.
On Thu, 2005-10-06 at 20:14, Nick Piggin wrote:
> Nigel Cunningham wrote:
> > From: Nigel Cunningham <nigel@suspend2.net>
> >
> > This patch removes the dependency that swap suspend currently has on
> > PageReserved. In the places where PageReserved is currently set and
> > cleared, we also set and clear PageNosave, and in swap suspend itself,
> > we only reference PageNosave. The ongoing effort at freeing PageReserved
> > thus achieves another step forward.
> >
>
> Any reason you can't use page_is_ram directly? I would rather you
> do this than moving swsusp specific flags out into the wider tree.
> The reason is that these flags now become just as hard to kill as
> PageReserved is.
>
> You'll have to slightly modify i386's page_is_ram, because it
> appears that you'll actually want
>
> 'page_is_ram(pfn) && !(bad_ppro && page_kills_ppro(pfn))'
Thanks for the suggestion!
I suppose we could do something like what you are suggesting. I'll take
a look. I'm not promising to do it immediately though - too busy trying
to finish off Suspend2 at the mo.
> Thanks, glad someone is looking into this!
Always glad to be of service!
Nigel
> Nick
--
prev parent reply other threads:[~2005-10-07 5:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 21:04 [PATCH] Free swap suspend from dependency on PageReserved Nigel Cunningham
2005-10-05 22:03 ` Dave Hansen
2005-10-05 22:24 ` Nigel Cunningham
2005-10-06 8:28 ` Rafael J. Wysocki
2005-10-06 10:14 ` Nick Piggin
2005-10-07 5:33 ` Nigel Cunningham [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=1128663205.13507.23.camel@localhost \
--to=ncunningham@cyclades.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=pavel@ucw.cz \
/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).