From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Linux Memory Management <linux-mm@kvack.org>,
Nigel Cunningham <ncunningham@cyclades.com>,
Pavel Machek <pavel@suse.cz>, Hugh Dickins <hugh@veritas.com>,
William Lee Irwin III <wli@holomorphy.com>
Subject: PageReserved removal from swsusp
Date: Mon, 25 Jul 2005 11:38:28 +1000 [thread overview]
Message-ID: <42E44294.5020408@yahoo.com.au> (raw)
Hi,
kernel/power/swsusp.c is the last remaining real user of PageReserved
with my current PageReserved removal patchset. This is actually not a
problem for my purposes, and swsusp is quite able to continue using
PageReserved... however that may be a bit ugly, and means swsusp will
be the sole user of 3(!) page-flags.
The PageReserved test in save_highmem_zone() is the hard one. rvmalloc
is no problem, but it seems to be important to prevent saving regions
that aren't RAM.
I seem to be able to work around this on i386 by testing page_is_ram()
instead of PageReserved, however that looks nonportable, and at least
on i386 we rather want something like page_is_usable_ram() which is
(page_is_ram && !(bad_ppro && page_kills_ppro))
Otherwise we could perhaps have a PageUsableRAM() which returns
page->flags != 0xffffffff or some other unlikely combination of flags.
They're my two ideas. Anyone else?
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
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 reply other threads:[~2005-07-25 1:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 1:38 Nick Piggin [this message]
2005-07-25 4:31 ` Nigel Cunningham
2005-07-25 4:52 ` Nick Piggin
2005-07-25 6:22 ` Nick Piggin
2005-07-25 6:59 ` Pavel Machek
2005-07-25 12:39 ` Hugh Dickins
2005-07-25 23:29 ` Nick Piggin
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=42E44294.5020408@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=ncunningham@cyclades.com \
--cc=pavel@suse.cz \
--cc=wli@holomorphy.com \
/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