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 14:25:17 +0000 [thread overview]
Message-ID: <1127831117.10315.91.camel@localhost> (raw)
In-Reply-To: <1127779977.10315.6.camel@localhost>
On Tue, 2005-09-27 at 07:45 -0500, Jack Steiner wrote:
> I haven't looked in detail at SPARSEMEM recently - is one config
> file for ALL hardware platforms easy to do without significantly
> compromising performance of any individual platform?
On the ppc64 and i386 machines where I've done testing, it hasn't been
an issue. Usually, the NUMA-Q is a nice canary and will fall over dead
if we're doing any large amount of crazy, new, cross-node accesses.
Compared to discontigmem, it actually gets a wee bit (~1-2%) faster on
thinks like kernbench and SDET.
But, we don't have a vmem_map on i386, so it's not an apples to apples
comparison. I'd love to see some head-to-head performance numbers,
though.
-- Dave
next prev parent reply other threads:[~2005-09-27 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 0:12 [Lhms-devel] Re: [PATCH 0/4] V4 ia64 SPARSEMEM Dave Hansen
2005-09-27 14:07 ` Bob Picco
2005-09-27 14:25 ` Dave Hansen [this message]
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=1127831117.10315.91.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