[dpdk-users] i need a help about invalid numasocket

[박준하]

thank you MAC Lee.
so if i want to connect my device with NUMA node.
what i should do?? 
 
-----Original Message-----
From: "MAC Lee"<mac_leehk at yahoo.com.hk> 
To: "박준하"<wnsgkqkr at naver.com>; 
Cc: 
Sent: 2017-12-20 (수) 13:50:08
Subject: RE: [dpdk-users] i need a help about invalid numasocket
 
Hi Shreyansh,    I think it can skip the message since you only have 1 numa node in your platform. And from your log, the print out should be came out from your application, right?hello from core 1hello from core 2hello from core 3hello from core 0    If there is any init failed, the print out will not came out.  Thanks,Marco 
     Mayank <mayank.patel at mayadata.io> 於 2017/12/20 (週三) 12:35 PM 寫道﹕   

 Hi Shreyansh,It seems that your device is not connected with NUMA node.On Wednesday 20 December 2017 07:53 AM, 박준하 wrote:> 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;shreyansh.jain at nxp.com&gt;> To: "박준하"&lt;wnsgkqkr at naver.com&gt;;> Cc: "users at dpdk.org"&lt;users at 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 at dpdk.org] On Behalf Of ???> &gt; Sent: Tuesday, December 19, 2017 4:10 PM> &gt; To: users at 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.