DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
Cc: Shreyansh Jain<shreyansh.jain@nxp.com>, <users@dpdk.org>
Subject: Re: [dpdk-users] i need a help about invalid numasocket
Date: Wed, 20 Dec 2017 07:14:17 -0800	[thread overview]
Message-ID: <20171220071417.55b5b022@xeon-e3> (raw)
In-Reply-To: <82844e9806f3a2145558cccfe0a29d@cweb25.nm.nhnsystem.com>

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 
>  
> I'm not sure because of it, i want to use tool PKTGEN.
> When i use this tool and start packet sending, its link is down and i can't send packet.
> I want to use this tool and make simulation.
> and also l2fwd doesn't work. 
>  
> root@jh-desktop:/home/jh/dpdk-17.11/examples/l2fwd# ./build/app/l2fwd -l 0-3 -n 1 -- -p 3
> 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
> MAC updating enabled
> Lcore 0: RX port 0
> Lcore 1: RX port 1
> Initializing port 0... PMD: ixgbe_dev_link_status_print():  Port 0: Link Down
> done: 
> Port 0, MAC address: 6C:B3:11:4F:1A:98
> 
> Initializing port 1... PMD: ixgbe_dev_link_status_print():  Port 1: Link Down
> done: 
> Port 1, MAC address: 6C:B3:11:4F:1A:9A 
>  
> -----Original Message-----
> From: "Shreyansh Jain"&lt;shreyansh.jain@nxp.com&gt; 
> To: "박준하"&lt;wnsgkqkr@naver.com&gt;; 
> Cc: "users@dpdk.org"&lt;users@dpdk.org&gt;; 
> Sent: 2017-12-20 (수) 14:50:15
> Subject: RE: [dpdk-users] i need a help about invalid numasocket
>  
> Hi,
> 
> I think your platform doesn’t have more than 1 NUMA node (node 0. See message " NUMA node(s):          1"). And you are giving ‘-n 4’ in command line.
> That might be the reason this warning is being reported before defaulting back to node 0.
> 
> Does this create any function issue? Like not having I/O in l2fwd/l3fwd application?
> 
> -
> Shreyansh
> 
> From: 박준하 [mailto:wnsgkqkr@naver.com] 
> Sent: Wednesday, December 20, 2017 7:54 AM
> To: Shreyansh Jain &lt;shreyansh.jain@nxp.com&gt;
> Cc: users@dpdk.org
> Subject: RE: [dpdk-users] i need a help about invalid numasocket
> 
> Thank you.
> this is my apllication result and lscpu and meminfo. 
>  
> result: lscpu | grep -i numa
> NUMA node(s):          1
> NUMA node0 CPU(s):     0-3
>  
> result: cat /proc/meminfo
> MemTotal:        7842552 kB
> MemFree:         1118008 kB
> MemAvailable:    2285580 kB
> Buffers:          109264 kB
> Cached:          1598564 kB
> SwapCached:            0 kB
> Active:          2352924 kB
> Inactive:         972164 kB
> Active(anon):    1622876 kB
> Inactive(anon):   370152 kB
> Active(file):     730048 kB
> Inactive(file):   602012 kB
> Unevictable:          16 kB
> Mlocked:              16 kB
> SwapTotal:       8051708 kB
> SwapFree:        8051708 kB
> Dirty:                68 kB
> Writeback:             0 kB
> AnonPages:       1298032 kB
> Mapped:           383092 kB
> Shmem:            375772 kB
> Slab:             152876 kB
> SReclaimable:     112428 kB
> SUnreclaim:        40448 kB
> KernelStack:       10528 kB
> PageTables:        38560 kB
> NFS_Unstable:          0 kB
> Bounce:                0 kB
> WritebackTmp:          0 kB
> CommitLimit:    10400120 kB
> Committed_AS:    6337284 kB
> VmallocTotal:   34359738367 kB
> VmallocUsed:           0 kB
> VmallocChunk:          0 kB
> HardwareCorrupted:     0 kB
> AnonHugePages:    460800 kB
> ShmemHugePages:        0 kB
> ShmemPmdMapped:        0 kB
> CmaTotal:              0 kB
> CmaFree:               0 kB
> HugePages_Total:    1024
> HugePages_Free:     1024
> HugePages_Rsvd:        0
> HugePages_Surp:        0
> Hugepagesize:       2048 kB
> DirectMap4k:      113688 kB
> DirectMap2M:     4794368 kB
> DirectMap1G:     3145728 kB
> 
> result: ./build/app/helloworld -l 0-3 -n 4
> 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
>  
> -----Original Message-----
> From: "Shreyansh Jain"&lt;mailto:shreyansh.jain@nxp.com&gt; 
> To: "박준하"&lt;mailto:wnsgkqkr@naver.com&gt;; 
> Cc: "mailto:users@dpdk.org"&lt;mailto:users@dpdk.org&gt;; 
> Sent: 2017-12-19 (화) 21:22:59
> Subject: RE: [dpdk-users] i need a help about invalid numasocket
>  
> &gt; -----Original Message-----
> &gt; From: users [mailto:users-bounces@dpdk.org] On Behalf Of ???
> &gt; Sent: Tuesday, December 19, 2017 4:10 PM
> &gt; To: mailto:users@dpdk.org
> &gt; Subject: [dpdk-users] i need a help about invalid numasocket
> &gt; 
> &gt; Hi, I used DPDK tools first before 1 week.
> &gt; I serached how to install and  follow them.
> &gt; I finally finished the setup hugepages, uio driver, bind device and make
> &gt; application.
> &gt; However, when i run the sample application(Helloworld) Memory allocation
> &gt; failed and result is invalid numasocket.
> &gt; 
> &gt; I really want to solve this help me. thank you
> &gt; 
> 
> I don't have a solution - but, I can suggest that if you can paste output of your execution here, someone might give you hints.
> Don't forget information about environment (platform, 'cat /proc/meminfo', etc). More the info about what you have attempted or trying to attempt, easier it is to point out possible problem area.


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

  reply	other threads:[~2017-12-20 15:14 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 [this message]
2017-12-20 15:27             ` Wiles, Keith

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=20171220071417.55b5b022@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=shreyansh.jain@nxp.com \
    --cc=users@dpdk.org \
    /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).