|| ||Nick Piggin <firstname.lastname@example.org>|
|| ||Andrew Morton <email@example.com>|
|| ||[patch 0/6] remove PageReserved|
|| ||Tue, 26 Jul 2005 18:15:53 +1000|
|| ||Hugh Dickins <firstname.lastname@example.org>,
Benjamin Herrenschmidt <email@example.com>,
If you're feeling like -mm is getting too stable, then you might
consider giving these patches a spin? (unless anyone else raises
Ben thought I should get moving with them soon.
Not much change from last time. A bit of ppc64 input from Ben,
and some rmap.c input from Hugh. Boots and runs on a few machines
I have lying around here.
The only remaining places that *test* PageReserved are swsusp, a
trivial useage in drivers/char/agp/amd64-agp.c, and arch/ code.
Most of the arch code is just reserved memory reporting, which
isn't very interesting and could easily be removed. Some arch users
are a bit more subtle, however they *should not* break, because all
the places that set and clear PageReserved are basically intact.
We can phase PageReserved out of the tree completely when the core
Now the main problems we might have are the introduction of some
tighter checks introduced by this patchset - for example 'bad_page'
is triggered on PG_reserved.
The other thing is - MAP_PRIVATE of VM_RESERVED regions becomes
disallowed. Any program that attempts such a thing prints a warning.
Hugh has some code which handles this case but he suggested that we
should first see whether it is even required.
Any thoughts? Comments?
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com