DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "@dpdk.org>" <wnsgkqkr@naver.com>,
	Shreyansh Jain <shreyansh.jain@nxp.com>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] i need a help about invalid numasocket
Date: Wed, 20 Dec 2017 15:27:47 +0000	[thread overview]
Message-ID: <33780C7F-FDED-4EF5-BD84-EB767AA517CA@intel.com> (raw)
In-Reply-To: <20171220071417.55b5b022@xeon-e3>



> On Dec 20, 2017, at 9:14 AM, Stephen Hemminger <stephen@networkplumber.org> wrote:
> 
> On Wed, 20 Dec 2017 16:56:00 +0900
> 박준하<wnsgkqkr@naver.com> wrote:
> 
>> Thank you Shreyansh Jain.
>> I tried to change -n 1 but i got same problem.
>> this is log.
>> 
>> root@jh-desktop:/home/jh/dpdk-17.11/examples/helloworld# ./build/app/helloworld -l 0-3 -n 1 
>> EAL: Detected 4 lcore(s)
>> EAL: Probing VFIO support...
>> EAL: PCI device 0000:00:1f.6 on NUMA socket -1
>> EAL:   Invalid NUMA socket, default to 0
>> EAL:   probe driver: 8086:15b8 net_e1000_em
>> EAL: PCI device 0000:01:00.0 on NUMA socket -1
>> EAL:   Invalid NUMA socket, default to 0
>> EAL:   probe driver: 8086:1528 net_ixgbe
>> EAL: PCI device 0000:01:00.1 on NUMA socket -1
>> EAL:   Invalid NUMA socket, default to 0
>> EAL:   probe driver: 8086:1528 net_ixgbe
>> hello from core 1
>> hello from core 2
>> hello from core 3
>> hello from core 0 
>> 
> 
> 
> Ignore the warning "Invalid NUMA socket" it is meaningless.
> If the platform does not support NUMA or kernel is compiled without NUMA support
> than the sysfs file for numa node is not present, and DPDK applications default
> to all 0

This is a case were the message Invalid NUMA should be changed to a DEBUG log and the ‘on NUMA socket -1’ should just report 0 not -1.

Regards,
Keith


      reply	other threads:[~2017-12-20 15:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <283f8a89e7d09260162064421dfa80@cweb09.nm.nhnsystem.com>
2017-12-19 10:40 ` 박준하
2017-12-19 12:22   ` Shreyansh Jain
2017-12-20  2:23     ` 박준하
2017-12-20  4:35       ` Mayank
     [not found]         ` <1744667063.1668474.1513745409006@mail.yahoo.com>
2017-12-20  7:48           ` 박준하
2017-12-20  5:50       ` Shreyansh Jain
2017-12-20  7:56         ` 박준하
2017-12-20 15:14           ` Stephen Hemminger
2017-12-20 15:27             ` Wiles, Keith [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=33780C7F-FDED-4EF5-BD84-EB767AA517CA@intel.com \
    --to=keith.wiles@intel.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    --cc=wnsgkqkr@naver.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).