All of lore.kernel.org
 help / color / mirror / Atom feed
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:22:53 -0700	[thread overview]
Message-ID: <1156785773.5913.38.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0608281003070.27677@schroedinger.engr.sgi.com>

On Mon, 2006-08-28 at 10:04 -0700, Christoph Lameter wrote:
> On Mon, 28 Aug 2006, Dave Hansen wrote:
> > -config IA64_PAGE_SIZE_64KB
> > -     depends on !ITANIUM
> > -     bool "64KB"
> > -
> > -endchoice
> 
> Uhh.. arch specific stuff in mm/Kconfig. Each arch needs to modify the 
> mm/Kconfig?

Yes and no.  First of all, 15 of the 24 architectures use the Kconfig
default of 4k pages.  Anybody adding an architecture with 4k pages only
has to include asm-generic/page.h in their arch, and they don't add
*anything* to Kconfig.  If they want completely fixed page sizes other
than 4k, they only add '|| ARCH' on one line in the Kconfig.

There are a couple of ways to go about enabling the configurable page
sizes.  One is to do what I did, hand have all of the architectures
enumerated in mm/Kconfig.  The other is to have something along the
lines of:

        choice
                prompt "Kernel Page Size"
                depends on ARCH_CHOOSES_PAGE_SIZE
        	...
        
Then in arch/{ia64,...}/Kconfig, have
        
        config ARCH_CHOOSES_PAGE_SIZE
        	def_bool y
        
That would be easy enough to do.  However, what I wanted to get out of
this was to be able to look at mm/Kconfig and get a really nice overview
of what *everybody* is doing.  I'd be more inclined to do the
ARCH_CHOOSES... stuff if the architecture-specific conditions were
actually complicated.  They really aren't.

Admittedly, this is a bit different from how it has been done
traditionally, but is is a really great tool for anyone working on
arch-generic code that wants to know "what architectures have an 8k page
size", or "what arches have a configurable page size".  This makes one
place to go look, with zero grepping.  

> Also cc linux-ia64@vger.kernel.org on these. 

Sure thing.

-- 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>

  reply	other threads:[~2006-08-28 17:22 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 [this message]
2006-08-28 17:32       ` Christoph Lameter
2006-08-28 17:45         ` Dave Hansen
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=1156785773.5913.38.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.