public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Franck <vagabon.xyz@gmail.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: Mon, 12 Jun 2006 09:10:03 -0700	[thread overview]
Message-ID: <1150128603.13644.28.camel@localhost.localdomain> (raw)
In-Reply-To: <448D1117.8010407@innova-card.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?

-- Dave


  reply	other threads:[~2006-06-12 16:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-12  7:00 [SPARSEMEM] confusing uses of SPARSEM_EXTREME (try #2) Franck Bui-Huu
2006-06-12 16:10 ` Dave Hansen [this message]
2006-06-13  8:51   ` Franck Bui-Huu
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=1150128603.13644.28.camel@localhost.localdomain \
    --to=haveblue@us.ibm.com \
    --cc=apw@shadowen.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vagabon.xyz@gmail.com \
    /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