From: Dave Hansen <haveblue@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Lhms-devel] Re: [PATCH 0/4] V4 ia64 SPARSEMEM
Date: Tue, 27 Sep 2005 00:12:57 +0000 [thread overview]
Message-ID: <1127779977.10315.6.camel@localhost> (raw)
On Mon, 2005-09-26 at 19:35 -0400, Bob Picco wrote:
> > regular scripts. Right now this whole change is a close to being
> > a no-op as none of the default configs enables SPARSEMEM.
>
> This is true and just about universally true for other arches with SPARSEMEM
> enabled. I took a quick look and only i386 selects SPARSEMEM for NUMA.
> I couldn't find any default config files with SPARSEMEM. I think the objective
> was for more soak time before defaulting to SPARSEMEM. Also just a few
> arches have SPARSEMEM support. Dave Hansen can possibly fill in my gaps.
Usually a change being an effective no-op for those that don't care is a
*plus* for a patch :)
In any case, no, it isn't the default for anything, yet. This is
partially because sparsemem isn't a universal win over discontig in all
cases. We wanted to allow a bit of choice. This phased introduction is
a bit smoother that just wiping out discontigmem completely.
On i386 it isn't the default because sparsemem is really only good in
places where discontig was used as well. i386 only uses discontig and
NUMA together. So, it was natural to keep the same relationship with
sparsemem.
-- Dave
next reply other threads:[~2005-09-27 0:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 0:12 Dave Hansen [this message]
2005-09-27 14:07 ` [Lhms-devel] Re: [PATCH 0/4] V4 ia64 SPARSEMEM Bob Picco
2005-09-27 14:25 ` Dave Hansen
2005-09-28 10:36 ` [Lhms-devel] " Bob Picco
2005-09-28 11:03 ` Robin Holt
2005-09-28 15:42 ` Bob Picco
2005-09-28 22:05 ` Greg Edwards
2005-09-28 22:10 ` Bruce Losure
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=1127779977.10315.6.camel@localhost \
--to=haveblue@us.ibm.com \
--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