From: Andi Kleen <andi@firstfloor.org>
To: Nix <nix@esperi.org.uk>
Cc: Andi Kleen <andi@firstfloor.org>, xb <xavier.bru@bull.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Xeon 5500 series support in kernel
Date: Sat, 4 Jul 2009 18:07:43 +0200 [thread overview]
Message-ID: <20090704160743.GA19804@basil.fritz.box> (raw)
In-Reply-To: <87k52o65gk.fsf@hades.wkstn.nix>
On Sat, Jul 04, 2009 at 12:41:15PM +0100, Nix wrote:
> On 2 Jul 2009, Andi Kleen outgrape:
>
> > xb <xavier.bru@bull.net> writes:
> >
> >> I wonder if there are specific kernel configuration parameters that
> >> allow to optimize performances on the recent Xeon 5500 processors (aka
> >> Nehalem).
> >
> > The most important optimization is to use a 64bit kernel with NUMA
> > support enabled (even if you use 32bit userland)
>
> Surely NUMA only benefits you if you have a >1 socket system? Where's
Xeons are typically multi socket. On single socket the overhead
of a NUMA kernel is negligible, so it's best to enable it always.
There are actually some use cases of NUMA kernel code for single
socket too, e.g. it is sometimes used to isolate different
applications on the VM level.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-07-04 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 8:59 Xeon 5500 series support in kernel xb
2009-07-02 9:46 ` Andi Kleen
2009-07-04 11:41 ` Nix
2009-07-04 16:07 ` Andi Kleen [this message]
2009-07-04 18:01 ` Morten P.D. Stevens
2009-07-05 9:55 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2009-07-02 7:45 lchampig
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=20090704160743.GA19804@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.org.uk \
--cc=xavier.bru@bull.net \
/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