From: Dave Hansen <haveblue@us.ibm.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-arch@vger.kernel.org
Subject: Re: [RFC][PATCH] unify all architecture PAGE_SIZE definitions
Date: Thu, 24 Aug 2006 17:23:44 -0700 [thread overview]
Message-ID: <1156465424.12011.159.camel@localhost.localdomain> (raw)
In-Reply-To: <20060825001459.GE3580@holomorphy.com>
On Thu, 2006-08-24 at 17:14 -0700, William Lee Irwin III wrote:
> With CONFIG_PAGE_SHIFT there doesn't need to be a CONFIG_PAGE_SIZE at
> all; just let #define PAGE_SIZE (1 << PAGE_SHIFT) handle it.
I think it does that:
> +#define PAGE_SHIFT CONFIG_PAGE_SHIFT
> +#define PAGE_SIZE (ASM_CONST(1) << PAGE_SHIFT)
Is it the Kconfig names themselves which you don't like? I guess it is
a bit silly to have CONFIG_PAGE_SIZE_X, defined to be number Y, which is
then calculated back to being X again. But, we were really already
doing that (in three places):
> -#if defined(CONFIG_SPARC64_PAGE_SIZE_8KB)
> -#define PAGE_SHIFT 13
> -#elif defined(CONFIG_SPARC64_PAGE_SIZE_64KB)
> -#define PAGE_SHIFT 16
> -#elif defined(CONFIG_SPARC64_PAGE_SIZE_512KB)
> -#define PAGE_SHIFT 19
> -#elif defined(CONFIG_SPARC64_PAGE_SIZE_4MB)
> -#define PAGE_SHIFT 22
> -#else
> -#error No page size specified in kernel configuration
> -#endif
But, unless users are willing to live with CONFIG_SMALLEST_PAGE,
CONFIG_SLIGHTLY_LESS_SMALL_PAGE, CONFIG_MEDIUM_SIZE_PAGE, etc... I'm not
sure what other names we can use. Does it seem any less objectionable
to think of the Kconfig options as just the names that we _present_ to
users?
-- Dave
next prev parent reply other threads:[~2006-08-25 0:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 23:44 [RFC][PATCH] unify all architecture PAGE_SIZE definitions Dave Hansen
2006-08-24 23:58 ` William Lee Irwin III
2006-08-25 0:07 ` Dave Hansen
2006-08-25 0:14 ` William Lee Irwin III
2006-08-25 0:23 ` Dave Hansen [this message]
2006-08-25 0:32 ` William Lee Irwin III
2006-08-25 8:12 ` Geert Uytterhoeven
2006-08-25 5:31 ` Paul Mundt
2006-08-25 15:03 ` Dave Hansen
2006-08-26 1:17 ` Paul Mundt
2006-08-25 21:04 ` Dave Hansen
2006-08-25 8:11 ` Geert Uytterhoeven
2006-08-25 14:55 ` Dave Hansen
2006-08-25 15:07 ` Geert Uytterhoeven
2006-08-25 17:16 ` David Howells
2006-08-25 17:31 ` Dave Hansen
2006-09-11 0:51 ` Jeff Dike
2006-09-11 17:33 ` Dave Hansen
2006-09-11 18:43 ` Dave Hansen
2006-09-11 23:40 ` Jeff Dike
2006-09-11 13:34 ` Ralf Baechle
2006-09-11 17:43 ` Dave Hansen
[not found] <BFECAF9E178F144FAEF2BF4CE739C66804016FA5@exmail1.se.axis.com>
2006-08-25 5:04 ` Mikael Starvik
-- strict thread matches above, loose matches on Subject: below --
2006-08-25 16:06 Luck, Tony
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=1156465424.12011.159.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=linux-arch@vger.kernel.org \
--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