From: Matthew Hall <mhall@mhcomputing.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Kevin Wilson <wkevils@gmail.com>, users@dpdk.org
Subject: Re: [dpdk-users] Which coremask and "-n" (number of mem channels) should be used for a system with only "node1" (no "node0") and 2 sockets ?
Date: Tue, 16 Aug 2016 11:09:39 -0700 [thread overview]
Message-ID: <20160816180939.GA27682@mhcomputing.net> (raw)
In-Reply-To: <20160816110526.144625fb@xeon-e3>
On Tue, Aug 16, 2016 at 11:05:26AM -0700, Stephen Hemminger wrote:
> What if you have a two socket machine, and node 0 is not populated?
I did include that possibility. But most NUMA systems I have set up myself
will not boot if Socket 1 is full and Socket 0 is empty. The early boot code
generally assumes Socket 0 is valid when first initting itself.
> Also does the kernel have NUMA support enabled?
Good question, the vast majority of standard SMP kernels do have NUMA at this
point I believe. It would maybe be good to see if the issue went away if the
machine was intentionally run with a UP kernel.
> Long ago there was a bug in DPDK where it got NUMA socket info from
> /proc/cpuinfo. On some machines, the 'physical id' starts at 1 because value
> comes from BIOS.
Ouch... that's very evil of the BIOS. But also sadly not surprising.
Matthew.
prev parent reply other threads:[~2016-08-16 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 6:51 Kevin Wilson
2016-07-18 19:13 ` Matthew Hall
2016-08-16 17:41 ` Kevin Wilson
2016-08-16 18:05 ` Stephen Hemminger
2016-08-16 18:09 ` Matthew Hall [this message]
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=20160816180939.GA27682@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
--cc=wkevils@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;
as well as URLs for NNTP newsgroup(s).