mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Franck Bui-Huu" <vagabon.xyz@gmail.com>
To: "Dave Hansen" <haveblue@us.ibm.com>
Cc: apw@shadowen.org,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [SPARSEMEM] confusing uses of SPARSEM_EXTREME (try #2)
Date: Tue, 13 Jun 2006 10:51:11 +0200	[thread overview]
Message-ID: <cda58cb80606130151k3d5eac15u163a6bf9eb5dfbcb@mail.gmail.com> (raw)
In-Reply-To: <1150128603.13644.28.camel@localhost.localdomain>

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

  reply	other threads:[~2006-06-13  8:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12  7:00 Franck Bui-Huu
2006-06-12 16:10 ` Dave Hansen
2006-06-13  8:51   ` Franck Bui-Huu [this message]
2006-06-12 16:25 ` Andy Whitcroft
2006-06-12 17:21   ` Franck Bui-Huu
2006-06-12 17:32     ` Andy Whitcroft
2006-06-13  8:34       ` Franck Bui-Huu
2006-06-13 10:05         ` Andy Whitcroft

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=cda58cb80606130151k3d5eac15u163a6bf9eb5dfbcb@mail.gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=apw@shadowen.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®