From: Andy Whitcroft <apw@shadowen.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [SPARSEMEM] confusing uses of SPARSEM_EXTREME (try #2)
Date: Mon, 12 Jun 2006 18:32:32 +0100 [thread overview]
Message-ID: <448DA530.7050604@shadowen.org> (raw)
In-Reply-To: <cda58cb80606121021w22207ef6yf6dfcbf428b144c3@mail.gmail.com>
Franck Bui-Huu wrote:
> Hi Andy
>
> 2006/6/12, Andy Whitcroft <apw@shadowen.org>:
>
>>
>> In my mind the positive option is selecting for code supporting EXTREME
>> so it seems to make sense to use that option.
>
>
> well I find it confusing because in my mind, something like this seems
> more logical.
>
> #ifndef CONFIG_SPARSEMEM_STATIC
> static struct mem_section *sparse_index_alloc(int nid)
> {
> return alloc_bootmem_node(...);
> }
> #else
> static struct mem_section *sparse_index_alloc(int nid)
> {
> /* nothing to do here, since it has been statically allocated */
> return 0;
> }
> #endif
But also in this case the code in the first stanza is only applicable to
SPARSEMEM EXTREME, therefore its also logical to say
#ifdef CONFIG_SPARSEMEM_EXTREME
special handling for that mode
#else
normal handling
#endif
Which is what the code currently says right?
-apw
next prev parent reply other threads:[~2006-06-12 17:32 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
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 [this message]
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=448DA530.7050604@shadowen.org \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.