lkml.org 
[lkml]   [2006]   [Jun]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [SPARSEMEM] confusing uses of SPARSEM_EXTREME (try #2)
Hi Dave,

2006/6/12, Dave Hansen <haveblue@us.ibm.com>:
> On Mon, 2006-06-12 at 09:00 +0200, Franck Bui-Huu wrote:
> > Is it me or the use of CONFIG_SPARSEMEM_EXTREME is really confusing in
> > mm/sparce.c ? Shouldn't we use CONFIG_SPARSEMEM_STATIC instead like
> > the following patch suggests ?
>
> I'll take positive config options over negative ones any day. I find it
> easier to read things that say what they *are* rather than what they are
> *not*.
>
> In any case, STATIC is really there as an override for architectures to
> say, "I know what I am doing, I use gcc 3.4 and above, or, I don't want
> to use bootmem". Extreme is really there to say, "I want two-level
> lookups because my memory is extremely sparse."
>
> Make sense?

yes and that's what the patch is trying to show...please take a look
to it and show me what part of the code, used by SPARSEMEM_STATIC
config, is dealing with the two-level lookups.

thanks
--
Franck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-06-13 10:53    [W:0.063 / U:4.840 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site