From: Dave Hansen <haveblue@us.ibm.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: CONFIG_PAGE_SHIFT (aka software PAGE_SIZE)
Date: Fri, 06 Jul 2007 16:33:21 -0700 [thread overview]
Message-ID: <1183764801.10287.233.camel@localhost> (raw)
In-Reply-To: <20070706222651.GG5777@v2.random>
On Sat, 2007-07-07 at 00:26 +0200, Andrea Arcangeli wrote:
> for the hack week at opensuse (see http://idea.opensuse.org/) I've
> been working on a new feature called CONFIG_PAGE_SHIFT.
...
> If you want to help/look here the patch:
>
> http://www.kernel.org/pub/linux/kernel/people/andrea/patches/v2.6/2.6.22-rc7/hard-page-size
>
> I'm tracking it with hg mq extension so far, but I can change if it
> helps.
The patch looks really interesting, it's just a little hard to parse
with all of the s/4096/PAGE_SIZE/ bits around. Those cleanups, along
with the s/PAGE_SIZE/HARD_PAGE_SIZE/ parts would be great in a
separated-out patch so that the really juicy bits (like the pte
handling) where the new logic is stand out better.
I think it would help readability to have something like:
#define PAGES_PER_HARD_PAGE (1<<(PAGE_SHIFT-HARD_PAGE_SHIFT))
which would look like this:
- if (unlikely(!pfn_valid(pfn))) {
+ if (unlikely(!pfn_valid(pfn * PAGES_PER_HARD_PAGE))) {
Instead of having hardpfn_t, would it be more useful to tag the types
with sparse? That's probably something that other interested parties
could work on.
-- Dave
next prev parent reply other threads:[~2007-07-06 23:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 22:26 RFC: CONFIG_PAGE_SHIFT (aka software PAGE_SIZE) Andrea Arcangeli
2007-07-06 23:33 ` Dave Hansen [this message]
2007-07-06 23:52 ` Andrea Arcangeli
2007-07-17 17:47 ` William Lee Irwin III
2007-07-17 19:33 ` Andrea Arcangeli
2007-07-18 13:32 ` William Lee Irwin III
2007-07-18 16:34 ` Rene Herman
2007-07-18 23:50 ` Andrea Arcangeli
2007-07-19 0:53 ` Rene Herman
2007-07-24 19:44 ` Andrea Arcangeli
2007-07-25 3:20 ` William Lee Irwin III
2007-07-25 14:39 ` Andrea Arcangeli
2007-07-25 17:56 ` William Lee Irwin III
2007-07-07 1:36 ` Badari Pulavarty
2007-07-07 1:47 ` Badari Pulavarty
2007-07-07 10:12 ` Andrea Arcangeli
2007-07-07 7:01 ` Paul Mackerras
2007-07-07 10:25 ` Andrea Arcangeli
2007-07-07 18:53 ` Jan Engelhardt
2007-07-07 20:34 ` Rik van Riel
2007-07-08 9:52 ` Andrea Arcangeli
2007-07-08 23:20 ` David Chinner
2007-07-10 10:11 ` Andrea Arcangeli
2007-07-12 0:12 ` David Chinner
2007-07-12 11:14 ` Andrea Arcangeli
2007-07-12 14:44 ` David Chinner
2007-07-12 16:31 ` Andrea Arcangeli
2007-07-12 16:34 ` Dave Hansen
2007-07-13 7:13 ` David Chinner
2007-07-13 14:08 ` Dave Kleikamp
2007-07-13 14:31 ` Andrea Arcangeli
2007-07-16 0:27 ` David Chinner
2007-07-12 17:53 ` Matt Mackall
2007-07-13 1:06 ` Andrea Arcangeli
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=1183764801.10287.233.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=andrea@suse.de \
--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