From: Nick Piggin <npiggin@suse.de>
To: linux-ia64@vger.kernel.org
Subject: discontigmem vs sparsemem on ia64 platforms
Date: Wed, 02 Sep 2009 16:38:10 +0000 [thread overview]
Message-ID: <20090902163810.GC28052@wotan.suse.de> (raw)
Hi guys,
I wonder why you have DISCONTIGMEM_DEFAULT selected for GENERIC, SN2, and ZX1?
You don't explicitly disable SPARSEMEM for those platforms I think, so is
there another reason than bugs for this?
My followup question... I wonder why memory hotplug is disabled for
discontigmem? It seems like there is code there to handle it (athough
I don't know the memory hotplug code well so I didn't look too closely).
Thanks,
Nick
next reply other threads:[~2009-09-02 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 16:38 Nick Piggin [this message]
2009-09-02 16:56 ` discontigmem vs sparsemem on ia64 platforms Luck, Tony
2009-09-02 17:12 ` Nick Piggin
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=20090902163810.GC28052@wotan.suse.de \
--to=npiggin@suse.de \
--cc=linux-ia64@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