public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Hugh Dickins <hugh@veritas.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [patch 0/6] remove PageReserved
Date: Tue, 26 Jul 2005 18:15:53 +1000	[thread overview]
Message-ID: <42E5F139.70002@yahoo.com.au> (raw)

Hi Andrew,

If you're feeling like -mm is getting too stable, then you might
consider giving these patches a spin? (unless anyone else raises
an objection).

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
becomes stable.

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 

             reply	other threads:[~2005-07-26  8:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26  8:15 Nick Piggin [this message]
2005-07-26  8:16 ` [patch 1/6] mm: comment rmap Nick Piggin
2005-07-26  8:17   ` [patch 2/6] mm: micro-optimise rmap Nick Piggin
2005-07-26  8:18     ` [patch 3/6] mm: cleanup rmap Nick Piggin
2005-07-26  8:19       ` [patch 4/6] mm: remove atomic Nick Piggin
2005-07-26  8:20         ` [patch 5/6] mm: remap ZERO_PAGE mappings Nick Piggin
2005-07-26  8:20           ` [patch 6/6] mm: core remove PageReserved Nick Piggin
2005-07-26  8:56             ` [patch 6/6] mm: core remove PageReserved (take 2) Nick Piggin
2005-07-27 11:30     ` [patch 2/6] mm: micro-optimise rmap Alexander Nyberg
2005-07-28  0:53       ` Nick Piggin
2005-07-26  8:21 ` [patch 0/6] remove PageReserved Nick Piggin
2005-07-26 13:09 ` Kumar Gala
2005-07-27  0:22   ` 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=42E5F139.70002@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    /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