From: Stephen Hemminger <stephen@networkplumber.org>
To: Kevin Wilson <wkevils@gmail.com>
Cc: Matthew Hall <mhall@mhcomputing.net>, 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:05:26 -0700 [thread overview]
Message-ID: <20160816110526.144625fb@xeon-e3> (raw)
In-Reply-To: <CAGXs5wWjogn52aL=HJCOKSHW2K8jRd4TrQiV0ETMDQ=BJRjPig@mail.gmail.com>
On Tue, 16 Aug 2016 20:41:42 +0300
Kevin Wilson <wkevils@gmail.com> wrote:
> Thanks Metthew.
> Indeed, something seems broken in that machine,
>
> Running
> dmidecode
> gives:
> .....
> Invalid entry length (0). DMI table is broken! Stop
>
> Kevin
>
>
> On Mon, Jul 18, 2016 at 10:13 PM, Matthew Hall <mhall@mhcomputing.net> wrote:
> > On Fri, Jul 15, 2016 at 09:51:42AM +0300, Kevin Wilson wrote:
> >> Hello,
> >> I have a machine on which there is a bit non common setup: I have only
> >> "node1" (no node0) under /sys/devices/system/node:
> >> ls /sys/devices/system/node/
> >> ...
> >> node1
> >> ...
> >
> > If I had to guess then either the BIOS is busted or the CPU is in the wrong
> > socket or the RAM is in the wrong socket.
> >
> > Either way all bets are off how this is going to pan out. Probably badly when
> > it comes to getting the top performance.
> >
> > Some exploration of the dmidecode output on the machine could be valuable.
> >
> > Matthew.
What if you have a two socket machine, and node 0 is not populated?
Also does the kernel have NUMA support enabled?
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.
next prev parent reply other threads:[~2016-08-16 18:05 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 [this message]
2016-08-16 18:09 ` Matthew Hall
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=20160816110526.144625fb@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=mhall@mhcomputing.net \
--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).