linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, apw@shadowen.org
Subject: Re: [RFC][PATCH 1/4] create mm/Kconfig for arch-independent memory options
Date: Fri, 25 Mar 2005 19:00:56 -0800	[thread overview]
Message-ID: <4244D068.3080900@osdl.org> (raw)
In-Reply-To: <E1DEwlP-0006BQ-00@kernel.beaverton.ibm.com>

Dave Hansen wrote:
> With sparsemem and memory hotplug there are quite a few options that
> we kept adding identically in several different architectures.  This
> new file allows some of these to be consolidated.
> 
> Signed-off-by: Andy Whitcroft <apw@shadowen.org>
> Signed-off-by: Dave Hansen <haveblue@us.ibm.com>
> ---
> 
>  memhotplug-dave/mm/Kconfig |   41 +++++++++++++++++++++++++++++++++++++++++
>  1 files changed, 41 insertions(+)
> 
> diff -puN mm/Kconfig~A6-mm-Kconfig mm/Kconfig
> --- memhotplug/mm/Kconfig~A6-mm-Kconfig	2005-03-25 08:08:22.000000000 -0800
> +++ memhotplug-dave/mm/Kconfig	2005-03-25 08:08:22.000000000 -0800
> @@ -0,0 +1,41 @@
> +choice
> +	prompt "Memory model"
> +	default FLATMEM
> +	default SPARSEMEM if ARCH_SPARSEMEM_DEFAULT
> +	default DISCONTIGMEM if ARCH_DISCONTIGMEM_DEFAULT
> +
> +config FLATMEM
> +	bool "Flat Memory"
> +	depends on !ARCH_DISCONTIGMEM_ENABLE || ARCH_FLATMEM_ENABLE
> +	help
> +	  This option allows you to change some of the ways that
> +	  Linux manages its memory internally.  Most users will
> +	  only have one option here: FLATMEM.  This is normal
> +	  and a correct option.
> +
> +	  Some users of more advanced features like NUMA and
> +	  memory hotplug may have different options here.
> +	  DISCONTIGMEM is an more mature, better tested system,
> +	  but is incompatible with memory hotplug and may suffer
> +	  decreased performance over SPARSEMEM.  If unsure between
> +	  "Sparse Memory" and "Discontiguous Memory", choose
Where is the "Sparse Memory" option?  I didn't find it.

> +	  "Discontiguous Memory".
> +
> +	  If unsure, choose FLATMEM.
> +
> +config DISCONTIGMEM
> +	bool "Discontigious Memory"
> +	depends on ARCH_DISCONTIGMEM_ENABLE
> +	help
> +	  If unsure, choose this option over "Sparse Memory".
Same question....

> +endchoice
> +
> +#
> +# Both the NUMA code and DISCONTIGMEM use arrays of pg_data_t's
> +# to represent different areas of memory.  This variable allows
> +# those dependencies to exist individually.
> +#
> +config NEED_MULTIPLE_NODES
> +	def_bool y
> +	depends on DISCONTIGMEM || NUMA


-- 
~Randy
--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2005-03-26  3:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-25 21:54 Dave Hansen
2005-03-26  3:00 ` Randy.Dunlap [this message]
2005-03-26 19:00   ` Dave Hansen
2005-03-26 20:56     ` Randy.Dunlap
2005-03-26 21:08       ` Dave Hansen
2005-03-26 21:38         ` 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=4244D068.3080900@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=apw@shadowen.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox