From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, Wang Sheng-Hui <shhuiw@gmail.com>
Subject: Re: [dpdk-dev] [PATCH] eal: fix linuxapp numa node detection
Date: Wed, 03 Jun 2015 18:07:44 +0200 [thread overview]
Message-ID: <4977448.shjjEWuQgn@xps13> (raw)
In-Reply-To: <20150422084457.42e50bd2@urahara>
2015-04-22 08:44, Stephen Hemminger:
> On Wed, 22 Apr 2015 14:31:55 +0100
> Bruce Richardson <bruce.richardson@intel.com> wrote:
>
> > Using the "physical_package_id" as a fallback for determining the
> > numa node of a core tends to be unreliable. Fix this by using a
> > detection routine which reads the numa information from
> > /sys/devices/system/node and just returns a numa node of 0 on
> > failure.
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
>
> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Applied, thanks
next prev parent reply other threads:[~2015-06-03 16:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 13:31 Bruce Richardson
2015-04-22 15:44 ` Stephen Hemminger
2015-06-03 16:07 ` Thomas Monjalon [this message]
2015-04-23 5:11 ` Ramia, Kannan Babu
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=4977448.shjjEWuQgn@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=shhuiw@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).