From: Dave Hansen <haveblue@us.ibm.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: [RFC][PATCH 2/7] ia64 generic PAGE_SIZE
Date: Mon, 28 Aug 2006 10:45:34 -0700 [thread overview]
Message-ID: <1156787134.5913.47.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0608281029550.27837@schroedinger.engr.sgi.com>
On Mon, 2006-08-28 at 10:32 -0700, Christoph Lameter wrote:
> Lets keep the arch specific stuff out of mm/Kconfig.
I know that the normal way of doing things has been with
ARCH_SUPPORTS_FOO defined in arch/Kconfig. But, I really like the
alternate approach because it is so easy to figure out which
architectures support which page sizes with a single glance at the
Kconfig file.
I can really see putting another layer of indirection in there if things
were too complicated to understand at a glance, but I think they've
remained pretty simple.
Is there any specific reason that you dislike the arch-specific stuff in
mm/Kconfig?
I don't mind creating those other Kconfig options, but I'm not really
sure I see a concrete reason for it, yet.
-- Dave
--
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 prev parent reply other threads:[~2006-08-28 17:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 15:44 [RFC][PATCH 1/7] generic PAGE_SIZE infrastructure (v2) Dave Hansen
2006-08-28 15:44 ` [RFC][PATCH 2/7] ia64 generic PAGE_SIZE Dave Hansen
2006-08-28 17:04 ` Christoph Lameter
2006-08-28 17:22 ` Dave Hansen
2006-08-28 17:32 ` Christoph Lameter
2006-08-28 17:45 ` Dave Hansen [this message]
2006-08-28 15:44 ` [RFC][PATCH 3/7] sparc64 " Dave Hansen
2006-08-28 15:44 ` [RFC][PATCH 4/7] mips " Dave Hansen
2006-08-28 15:44 ` [RFC][PATCH 6/7] powerpc " Dave Hansen
2006-08-28 15:44 ` [RFC][PATCH 5/7] parisc " Dave Hansen
2006-08-28 15:44 ` [RFC][PATCH 7/7] convert the "easy" architectures to " Dave Hansen
2006-08-28 17:01 ` [RFC][PATCH 1/7] generic PAGE_SIZE infrastructure (v2) Christoph Lameter
2006-08-28 17:11 ` Dave Hansen
2006-08-28 23:32 ` Peter Chubb
2006-08-29 18:59 ` Dave Hansen
2006-08-28 20:53 ` Dave Hansen
2006-08-28 21:44 ` Christoph Lameter
2006-08-29 2:46 ` Paul Mundt
2006-08-29 3:51 ` Randy.Dunlap
2006-08-29 3:55 ` Paul Mundt
2006-08-29 4:02 ` Randy.Dunlap
2006-08-29 15:29 ` Dave Hansen
2006-08-30 0:37 ` Randy.Dunlap
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=1156787134.5913.47.camel@localhost.localdomain \
--to=haveblue@us.ibm.com \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.