From: Matthew Hall <mhall@mhcomputing.net>
To: Kevin Wilson <wkevils@gmail.com>
Cc: 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: Mon, 18 Jul 2016 12:13:50 -0700 [thread overview]
Message-ID: <20160718191350.GB19151@mhcomputing.net> (raw)
In-Reply-To: <CAGXs5wURCtVK1DrTZ53sacZLFZ3vARXFgVzZN7uMg6y0dF5TyQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2016-07-18 19:13 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 [this message]
2016-08-16 17:41 ` Kevin Wilson
2016-08-16 18:05 ` Stephen Hemminger
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=20160718191350.GB19151@mhcomputing.net \
--to=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).