Hi Roman,
How does the attached patch look? It will still give us the flexibility
to override the memory models, but only in the presence of
CONFIG_EXPERIMENTAL.
It also adds some better help text to the DISCONTIGMEM menu. Is that
something like what you were looking for?
-- Dave
---
On Thu, 2005-04-07 at 02:30 +0200, Roman Zippel wrote:
> I was hoping for this too, in the meantime can't you simply make it a
> suboption of DISCONTIGMEM? So an extra option is only visible when it's
> enabled and most people can ignore it completely by just disabling a
> single option.
On Thu, 2005-04-07 at 02:30 +0200, Roman Zippel wrote:
I was hoping for this too, in the meantime can't you simply make it a
suboption of DISCONTIGMEM? So an extra option is only visible when it's
enabled and most people can ignore it completely by just disabling a
single option.
That's
Hi Roman,
How does the attached patch look? It will still give us the flexibility
to override the memory models, but only in the presence of
CONFIG_EXPERIMENTAL.
It also adds some better help text to the DISCONTIGMEM menu. Is that
something like what you were looking for?
-- Dave
---
Hi,
On Wed, 6 Apr 2005, Dave Hansen wrote:
> > Why is this choice needed at all? Why would one choose SPARSEMEM over
> > DISCONTIGMEM?
>
> For now, it's only so people can test either one, and we don't have to
> try to toss DICONTIGMEM out of the kernel in fell swoop. When the
> memory
On Thu, 2005-04-07 at 01:40 +0200, Roman Zippel wrote:
> On Wed, 6 Apr 2005, Dave Hansen wrote:
> > On Wed, 2005-04-06 at 22:58 +0200, Roman Zippel wrote:
> > > Dave Hansen wrote:
> > > > --- memhotplug/mm/Kconfig~A6-mm-Kconfig 2005-04-04 09:04:48.0
> > > > -0700
> > > > +++
Hi,
On Wed, 6 Apr 2005, Dave Hansen wrote:
> On Wed, 2005-04-06 at 22:58 +0200, Roman Zippel wrote:
> > Dave Hansen wrote:
> > > --- memhotplug/mm/Kconfig~A6-mm-Kconfig 2005-04-04 09:04:48.0
> > > -0700
> > > +++ memhotplug-dave/mm/Kconfig2005-04-04 10:15:23.0 -0700
> > >
On Wed, 2005-04-06 at 22:58 +0200, Roman Zippel wrote:
> Dave Hansen wrote:
> > --- memhotplug/mm/Kconfig~A6-mm-Kconfig 2005-04-04 09:04:48.0
> > -0700
> > +++ memhotplug-dave/mm/Kconfig 2005-04-04 10:15:23.0 -0700
> > @@ -0,0 +1,25 @@
> > +choice
> > + prompt "Memory
Hi,
Dave Hansen wrote:
> diff -puN mm/Kconfig~A6-mm-Kconfig mm/Kconfig
> --- memhotplug/mm/Kconfig~A6-mm-Kconfig 2005-04-04 09:04:48.0
> -0700
> +++ memhotplug-dave/mm/Kconfig2005-04-04 10:15:23.0 -0700
> @@ -0,0 +1,25 @@
> +choice
> + prompt "Memory model"
> +
Hi,
Dave Hansen wrote:
diff -puN mm/Kconfig~A6-mm-Kconfig mm/Kconfig
--- memhotplug/mm/Kconfig~A6-mm-Kconfig 2005-04-04 09:04:48.0
-0700
+++ memhotplug-dave/mm/Kconfig2005-04-04 10:15:23.0 -0700
@@ -0,0 +1,25 @@
+choice
+ prompt Memory model
+
On Wed, 2005-04-06 at 22:58 +0200, Roman Zippel wrote:
Dave Hansen wrote:
--- memhotplug/mm/Kconfig~A6-mm-Kconfig 2005-04-04 09:04:48.0
-0700
+++ memhotplug-dave/mm/Kconfig 2005-04-04 10:15:23.0 -0700
@@ -0,0 +1,25 @@
+choice
+ prompt Memory model
+
Hi,
On Wed, 6 Apr 2005, Dave Hansen wrote:
On Wed, 2005-04-06 at 22:58 +0200, Roman Zippel wrote:
Dave Hansen wrote:
--- memhotplug/mm/Kconfig~A6-mm-Kconfig 2005-04-04 09:04:48.0
-0700
+++ memhotplug-dave/mm/Kconfig2005-04-04 10:15:23.0 -0700
@@ -0,0 +1,25
On Thu, 2005-04-07 at 01:40 +0200, Roman Zippel wrote:
On Wed, 6 Apr 2005, Dave Hansen wrote:
On Wed, 2005-04-06 at 22:58 +0200, Roman Zippel wrote:
Dave Hansen wrote:
--- memhotplug/mm/Kconfig~A6-mm-Kconfig 2005-04-04 09:04:48.0
-0700
+++ memhotplug-dave/mm/Kconfig
Hi,
On Wed, 6 Apr 2005, Dave Hansen wrote:
Why is this choice needed at all? Why would one choose SPARSEMEM over
DISCONTIGMEM?
For now, it's only so people can test either one, and we don't have to
try to toss DICONTIGMEM out of the kernel in fell swoop. When the
memory hotplug
On Mon, Apr 04, 2005 at 10:50:09AM -0700, Dave Hansen wrote:
diff -puN mm/Kconfig~A6-mm-Kconfig mm/Kconfig
--- memhotplug/mm/Kconfig~A6-mm-Kconfig 2005-04-04 09:04:48.0 -0700
+++ memhotplug-dave/mm/Kconfig 2005-04-04 10:15:23.0 -0700
@@ -0,0 +1,25 @@
> +choice
> + prompt
On Mon, 2005-04-04 at 16:22 -0700, Mike Kravetz wrote:
> Do you need to set ARCH_DISCONTIGMEM_DEFAULT instead of just
> CONFIG_ARCH_DISCONTIGMEM_ENABLE to have DISCONTIGMEM be the
> default? or am I missing something? I don't see
> ARCH_DISCONTIGMEM_DEFAULT turned on by default in any of these
>
With sparsemem being introduced, we need a central place for new
memory-related .config options: mm/Kconfig. This allows us to
remove many of the duplicated arch-specific options.
The new option, CONFIG_FLATMEM, is there to enable us to detangle
NUMA and DISCONTIGMEM. This is a requirement for
With sparsemem being introduced, we need a central place for new
memory-related .config options: mm/Kconfig. This allows us to
remove many of the duplicated arch-specific options.
The new option, CONFIG_FLATMEM, is there to enable us to detangle
NUMA and DISCONTIGMEM. This is a requirement for
On Mon, 2005-04-04 at 16:22 -0700, Mike Kravetz wrote:
Do you need to set ARCH_DISCONTIGMEM_DEFAULT instead of just
CONFIG_ARCH_DISCONTIGMEM_ENABLE to have DISCONTIGMEM be the
default? or am I missing something? I don't see
ARCH_DISCONTIGMEM_DEFAULT turned on by default in any of these
On Mon, Apr 04, 2005 at 10:50:09AM -0700, Dave Hansen wrote:
diff -puN mm/Kconfig~A6-mm-Kconfig mm/Kconfig
--- memhotplug/mm/Kconfig~A6-mm-Kconfig 2005-04-04 09:04:48.0 -0700
+++ memhotplug-dave/mm/Kconfig 2005-04-04 10:15:23.0 -0700
@@ -0,0 +1,25 @@
+choice
+ prompt Memory
Dave Hansen wrote:
On Sat, 2005-03-26 at 12:56 -0800, Randy.Dunlap wrote:
I wasn't trying to catch you, but I've already looked at
all 4 patches in the series and I still can't find an
option that is labeled/described as "Sparse Memory"
The word "sparse" isn't even in patch 3/4... maybe
there
On Sat, 2005-03-26 at 12:56 -0800, Randy.Dunlap wrote:
> I wasn't trying to catch you, but I've already looked at
> all 4 patches in the series and I still can't find an
> option that is labeled/described as "Sparse Memory"
> The word "sparse" isn't even in patch 3/4... maybe
> there is
Dave Hansen wrote:
On Fri, 2005-03-25 at 19:00 -0800, Randy.Dunlap wrote:
...
+config DISCONTIGMEM
+ bool "Discontigious Memory"
+ depends on ARCH_DISCONTIGMEM_ENABLE
+ help
+ If unsure, choose this option over "Sparse Memory".
Same question
It's in the third patch
On Fri, 2005-03-25 at 19:00 -0800, Randy.Dunlap wrote:
...
> > +config DISCONTIGMEM
> > + bool "Discontigious Memory"
> > + depends on ARCH_DISCONTIGMEM_ENABLE
> > + help
> > + If unsure, choose this option over "Sparse Memory".
> Same question
It's in the third patch in the series.
On Fri, 2005-03-25 at 19:00 -0800, Randy.Dunlap wrote:
...
+config DISCONTIGMEM
+ bool Discontigious Memory
+ depends on ARCH_DISCONTIGMEM_ENABLE
+ help
+ If unsure, choose this option over Sparse Memory.
Same question
It's in the third patch in the series. They were all
Dave Hansen wrote:
On Fri, 2005-03-25 at 19:00 -0800, Randy.Dunlap wrote:
...
+config DISCONTIGMEM
+ bool Discontigious Memory
+ depends on ARCH_DISCONTIGMEM_ENABLE
+ help
+ If unsure, choose this option over Sparse Memory.
Same question
It's in the third patch in
On Sat, 2005-03-26 at 12:56 -0800, Randy.Dunlap wrote:
I wasn't trying to catch you, but I've already looked at
all 4 patches in the series and I still can't find an
option that is labeled/described as Sparse Memory
The word sparse isn't even in patch 3/4... maybe
there is something
Dave Hansen wrote:
On Sat, 2005-03-26 at 12:56 -0800, Randy.Dunlap wrote:
I wasn't trying to catch you, but I've already looked at
all 4 patches in the series and I still can't find an
option that is labeled/described as Sparse Memory
The word sparse isn't even in patch 3/4... maybe
there is
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 <[EMAIL PROTECTED]>
Signed-off-by: Dave Hansen <[EMAIL
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 <[EMAIL PROTECTED]>
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
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 [EMAIL PROTECTED]
Signed-off-by: Dave Hansen [EMAIL PROTECTED]
---
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 [EMAIL PROTECTED]
Signed-off-by: Dave Hansen [EMAIL
32 matches
Mail list logo
