From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-numa@vger.kernel.org,
Alan Piszcz <ap@solarrain.com>
Subject: Re: 3.1-rc2: CONFIG_NUMA Question
Date: Thu, 18 Aug 2011 07:59:26 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1108180758290.7903@p34.internal.lan> (raw)
In-Reply-To: <CAM_iQpWPaavsa7gSURP5CL8+Es2P5rEdtLRmrOx+wQkThX7v9w@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1470 bytes --]
On Thu, 18 Aug 2011, Américo Wang wrote:
> On Thu, Aug 18, 2011 at 6:51 PM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>> Hi,
>>
>> I have a SuperMicro X8DTH-6F motherboard with 2 cpus it has NUMA options in
>> the BIOS; what parameters/should I be using for the NUMA options in the
>> kernel?
>>
>> | | [*] Numa Memory Allocation and Scheduler Support | |
>> | | [ ] Old style AMD Opteron NUMA detection | |
>> | | [*] ACPI NUMA detection | |
>> | | [ ] NUMA emulation | |
>> | | (6) Maximum NUMA Nodes (as a power of 2) | |
>>
>
> That is Intel processor, right? If so, the things you selected here are enough,
Hi, yes-- two Intel Xeon E5645s.
> the rest two is not what you need.
Ok.
>
>> Specifically, the maximum number of NUMA nodes? Will this help to increase
>> performance of large memory allocations/is there any downside
>> to enabling this feature?
>
> The max of NUMA nodes is specified by CONFIG_NODES_SHIFT,
> in your case, it is 6, which means it supports up to 2^6 nodes.
Ok, is there any overhead having more than is needed?
>
> If your hardware supports NUMA, yes, that certainly help to increase
> the performance.
Nice, thanks.
Justin.
next prev parent reply other threads:[~2011-08-18 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-18 10:51 Justin Piszcz
2011-08-18 11:51 ` Américo Wang
2011-08-18 11:59 ` Justin Piszcz [this message]
2011-08-19 19:25 ` David Rientjes
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=alpine.DEB.2.02.1108180758290.7903@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-numa@vger.kernel.org \
--cc=xiyou.wangcong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®