[dpdk-users] Issue on running kni application

[dpdk-users] Issue on running kni application

[Nikhila, Athaluri (Nokia - IN/Bangalore)]

Hi,

     I am trying to run the kni application which is an example of DPDK and I am getting the following error. Can anyone please help me out.

Hugepages - 303 hugepages (2 MB)
Error: exiting with code 1
 Cause : could not initialize mbuf pool.

Thanks in advance.


sudo ./build/app/kni -c 0xf -n 4 -- -P -p 0x3 --config="(0,0,1),(1,2,3)"
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f0ee1600000 (size = 0x600000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0ee1200000 (size = 0x200000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f0ee0c00000 (size = 0x400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0ee0800000 (size = 0x200000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f0ee0000000 (size = 0x600000)
EAL: Ask a virtual area of 0x4800000 bytes
EAL: Virtual area found at 0x7f0edb600000 (size = 0x4800000)
EAL: Ask a virtual area of 0x4c00000 bytes
EAL: Virtual area found at 0x7f0ed6800000 (size = 0x4c00000)
EAL: Ask a virtual area of 0x1e00000 bytes
EAL: Virtual area found at 0x7f0ed4800000 (size = 0x1e00000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f0ed3a00000 (size = 0xc00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0ed3600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0ed3200000 (size = 0x200000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f0ed2c00000 (size = 0x400000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f0ed2400000 (size = 0x600000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0ed2000000 (size = 0x200000)
EAL: Ask a virtual area of 0x800000 bytes
EAL: Virtual area found at 0x7f0ed1600000 (size = 0x800000)
EAL: Ask a virtual area of 0x800000 bytes
EAL: Virtual area found at 0x7f0ed0c00000 (size = 0x800000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0ed0800000 (size = 0x200000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f0ed0000000 (size = 0x600000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f0ecf800000 (size = 0x600000)
EAL: Ask a virtual area of 0x1c00000 bytes
EAL: Virtual area found at 0x7f0ecda00000 (size = 0x1c00000)
EAL: Ask a virtual area of 0x2800000 bytes
EAL: Virtual area found at 0x7f0ecb000000 (size = 0x2800000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0ecac00000 (size = 0x200000)
EAL: Ask a virtual area of 0x4600000 bytes
EAL: Virtual area found at 0x7f0ec6400000 (size = 0x4600000)
EAL: Ask a virtual area of 0x1c00000 bytes
EAL: Virtual area found at 0x7f0ec4600000 (size = 0x1c00000)
EAL: Ask a virtual area of 0xe00000 bytes
EAL: Virtual area found at 0x7f0ec3600000 (size = 0xe00000)
EAL: Ask a virtual area of 0x2000000 bytes
EAL: Virtual area found at 0x7f0ec1400000 (size = 0x2000000)
EAL: Ask a virtual area of 0x1200000 bytes
EAL: Virtual area found at 0x7f0ec0000000 (size = 0x1200000)
EAL: Ask a virtual area of 0x1000000 bytes
EAL: Virtual area found at 0x7f0ebee00000 (size = 0x1000000)
EAL: Ask a virtual area of 0xa00000 bytes
EAL: Virtual area found at 0x7f0ebe200000 (size = 0xa00000)
EAL: Ask a virtual area of 0x600000 bytes
EAL: Virtual area found at 0x7f0ebda00000 (size = 0x600000)
EAL: Ask a virtual area of 0xa00000 bytes
EAL: Virtual area found at 0x7f0ebce00000 (size = 0xa00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0ebca00000 (size = 0x200000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7f0ebc400000 (size = 0x400000)
EAL: Ask a virtual area of 0x1400000 bytes
EAL: Virtual area found at 0x7f0ebae00000 (size = 0x1400000)
EAL: Ask a virtual area of 0x800000 bytes
EAL: Virtual area found at 0x7f0eba400000 (size = 0x800000)
EAL: Ask a virtual area of 0x800000 bytes
EAL: Virtual area found at 0x7f0eb9a00000 (size = 0x800000)
EAL: Ask a virtual area of 0xc00000 bytes
EAL: Virtual area found at 0x7f0eb8c00000 (size = 0xc00000)
EAL: Ask a virtual area of 0x1000000 bytes
EAL: Virtual area found at 0x7f0eb7a00000 (size = 0x1000000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0eb7600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0eb7200000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f0eb6e00000 (size = 0x200000)
EAL: Requesting 303 pages of size 2MB from socket 0
EAL: TSC frequency is ~2690619 KHz
EAL: Master lcore 0 is ready (tid=e428f900;cpuset=[0])
EAL: lcore 3 is ready (tid=b5dfd700;cpuset=[3])
EAL: lcore 1 is ready (tid=b6dff700;cpuset=[1])
EAL: lcore 2 is ready (tid=b65fe700;cpuset=[2])
EAL: PCI device 0000:00:03.0 on NUMA socket -1
EAL:   probe driver: 8086:100e rte_em_pmd
EAL:   PCI memory mapped at 0x7f0ee1c00000
PMD: eth_em_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x100e
EAL: PCI device 0000:00:08.0 on NUMA socket -1
EAL:   probe driver: 8086:100e rte_em_pmd
EAL:   PCI memory mapped at 0x7f0ee1c20000
PMD: eth_em_dev_init(): port_id 1 vendorID=0x8086 deviceID=0x100e
EAL: PCI device 0000:00:09.0 on NUMA socket -1
EAL:   probe driver: 8086:100e rte_em_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:00:0a.0 on NUMA socket -1
EAL:   probe driver: 8086:100e rte_em_pmd
EAL:   Not managed by a supported kernel driver, skipped
APP: Port ID: 0
APP: Rx lcore ID: 0, Tx lcore ID: 1
APP: Port ID: 1
APP: Rx lcore ID: 2, Tx lcore ID: 3
EAL: Error - exiting with code: 1
  Cause: Could not initialise mbuf pool

Re: [dpdk-users] Issue on running kni application

[SAKTHIVEL ANAND S]

Hi
Not sure , how much memory needed for KNI application. I am using 2MB *
1024 pages and it is working fine.That is enough i guess. for setting up
hugepages /tools/setup.sh <option 21>

Thanks
Sakthivel S

On Fri, Apr 15, 2016 at 10:53 AM, Nikhila, Athaluri (Nokia - IN/Bangalore) <
athaluri.nikhila@nokia.com> wrote:

> Hi,
>
>      I am trying to run the kni application which is an example of DPDK
> and I am getting the following error. Can anyone please help me out.
>
> Hugepages - 303 hugepages (2 MB)
> Error: exiting with code 1
>  Cause : could not initialize mbuf pool.
>
> Thanks in advance.
>
>
> sudo ./build/app/kni -c 0xf -n 4 -- -P -p 0x3 --config="(0,0,1),(1,2,3)"
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 4 lcore(s)
> EAL: Setting up physically contiguous memory...
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7f0ee1600000 (size = 0x600000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ee1200000 (size = 0x200000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7f0ee0c00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ee0800000 (size = 0x200000)
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7f0ee0000000 (size = 0x600000)
> EAL: Ask a virtual area of 0x4800000 bytes
> EAL: Virtual area found at 0x7f0edb600000 (size = 0x4800000)
> EAL: Ask a virtual area of 0x4c00000 bytes
> EAL: Virtual area found at 0x7f0ed6800000 (size = 0x4c00000)
> EAL: Ask a virtual area of 0x1e00000 bytes
> EAL: Virtual area found at 0x7f0ed4800000 (size = 0x1e00000)
> EAL: Ask a virtual area of 0xc00000 bytes
> EAL: Virtual area found at 0x7f0ed3a00000 (size = 0xc00000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ed3600000 (size = 0x200000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ed3200000 (size = 0x200000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7f0ed2c00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7f0ed2400000 (size = 0x600000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ed2000000 (size = 0x200000)
> EAL: Ask a virtual area of 0x800000 bytes
> EAL: Virtual area found at 0x7f0ed1600000 (size = 0x800000)
> EAL: Ask a virtual area of 0x800000 bytes
> EAL: Virtual area found at 0x7f0ed0c00000 (size = 0x800000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ed0800000 (size = 0x200000)
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7f0ed0000000 (size = 0x600000)
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7f0ecf800000 (size = 0x600000)
> EAL: Ask a virtual area of 0x1c00000 bytes
> EAL: Virtual area found at 0x7f0ecda00000 (size = 0x1c00000)
> EAL: Ask a virtual area of 0x2800000 bytes
> EAL: Virtual area found at 0x7f0ecb000000 (size = 0x2800000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ecac00000 (size = 0x200000)
> EAL: Ask a virtual area of 0x4600000 bytes
> EAL: Virtual area found at 0x7f0ec6400000 (size = 0x4600000)
> EAL: Ask a virtual area of 0x1c00000 bytes
> EAL: Virtual area found at 0x7f0ec4600000 (size = 0x1c00000)
> EAL: Ask a virtual area of 0xe00000 bytes
> EAL: Virtual area found at 0x7f0ec3600000 (size = 0xe00000)
> EAL: Ask a virtual area of 0x2000000 bytes
> EAL: Virtual area found at 0x7f0ec1400000 (size = 0x2000000)
> EAL: Ask a virtual area of 0x1200000 bytes
> EAL: Virtual area found at 0x7f0ec0000000 (size = 0x1200000)
> EAL: Ask a virtual area of 0x1000000 bytes
> EAL: Virtual area found at 0x7f0ebee00000 (size = 0x1000000)
> EAL: Ask a virtual area of 0xa00000 bytes
> EAL: Virtual area found at 0x7f0ebe200000 (size = 0xa00000)
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7f0ebda00000 (size = 0x600000)
> EAL: Ask a virtual area of 0xa00000 bytes
> EAL: Virtual area found at 0x7f0ebce00000 (size = 0xa00000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ebca00000 (size = 0x200000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7f0ebc400000 (size = 0x400000)
> EAL: Ask a virtual area of 0x1400000 bytes
> EAL: Virtual area found at 0x7f0ebae00000 (size = 0x1400000)
> EAL: Ask a virtual area of 0x800000 bytes
> EAL: Virtual area found at 0x7f0eba400000 (size = 0x800000)
> EAL: Ask a virtual area of 0x800000 bytes
> EAL: Virtual area found at 0x7f0eb9a00000 (size = 0x800000)
> EAL: Ask a virtual area of 0xc00000 bytes
> EAL: Virtual area found at 0x7f0eb8c00000 (size = 0xc00000)
> EAL: Ask a virtual area of 0x1000000 bytes
> EAL: Virtual area found at 0x7f0eb7a00000 (size = 0x1000000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0eb7600000 (size = 0x200000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0eb7200000 (size = 0x200000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0eb6e00000 (size = 0x200000)
> EAL: Requesting 303 pages of size 2MB from socket 0
> EAL: TSC frequency is ~2690619 KHz
> EAL: Master lcore 0 is ready (tid=e428f900;cpuset=[0])
> EAL: lcore 3 is ready (tid=b5dfd700;cpuset=[3])
> EAL: lcore 1 is ready (tid=b6dff700;cpuset=[1])
> EAL: lcore 2 is ready (tid=b65fe700;cpuset=[2])
> EAL: PCI device 0000:00:03.0 on NUMA socket -1
> EAL:   probe driver: 8086:100e rte_em_pmd
> EAL:   PCI memory mapped at 0x7f0ee1c00000
> PMD: eth_em_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x100e
> EAL: PCI device 0000:00:08.0 on NUMA socket -1
> EAL:   probe driver: 8086:100e rte_em_pmd
> EAL:   PCI memory mapped at 0x7f0ee1c20000
> PMD: eth_em_dev_init(): port_id 1 vendorID=0x8086 deviceID=0x100e
> EAL: PCI device 0000:00:09.0 on NUMA socket -1
> EAL:   probe driver: 8086:100e rte_em_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:00:0a.0 on NUMA socket -1
> EAL:   probe driver: 8086:100e rte_em_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> APP: Port ID: 0
> APP: Rx lcore ID: 0, Tx lcore ID: 1
> APP: Port ID: 1
> APP: Rx lcore ID: 2, Tx lcore ID: 3
> EAL: Error - exiting with code: 1
>   Cause: Could not initialise mbuf pool
>
>

Re: [dpdk-users] Issue on running kni application

[SAKTHIVEL ANAND S]

Hi

I was about to say that , you have to change(increase) the hugepages. To be
simple , please follow the below step to increase number of hugepages(from
my script) and then run your KNI app.


#setting huge pages for DPDK program
mkdir -p /mnt/huge

mount -t hugetlbfs nodev /mnt/huge

echo 1024 >
/sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages

you can cross check (last few lines):  cat /proc/meminfo

Regards
Sakthivel S

On Mon, Apr 18, 2016 at 10:10 AM, Nikhila, Athaluri (Nokia - IN/Bangalore) <
athaluri.nikhila@nokia.com> wrote:

> Hi,
>
>
>
>                 When I check option 21 ,I get the following details.
>
>
>
> Option: 21
>
> chmod /dev/vfio
> OK
> chmod /dev/vfio/*
> OK
>
> Current user memlock limit: 0 MB
>
> This is the maximum amount of memory you will be
> able to use with DPDK and VFIO if run as current user.
> To change this, please adjust limits.conf memlock limit for current user.
>
> ## WARNING: memlock limit is less than 64MB
> ## DPDK with VFIO may not be able to initialize if run as current user.
>
>
>
> Rgds,
>
> Nikhila
>
>
>
>
>
> *From:* EXT SAKTHIVEL ANAND S [mailto:anand.sa88@gmail.com]
> *Sent:* Friday, April 15, 2016 6:15 PM
> *To:* Nikhila, Athaluri (Nokia - IN/Bangalore) <athaluri.nikhila@nokia.com
> >
> *Cc:* users@dpdk.org
> *Subject:* Re: [dpdk-users] Issue on running kni application
>
>
>
> Hi
> Not sure , how much memory needed for KNI application. I am using 2MB *
> 1024 pages and it is working fine.That is enough i guess. for setting up
> hugepages /tools/setup.sh <option 21>
>
> Thanks
>
> Sakthivel S
>
>
>
> On Fri, Apr 15, 2016 at 10:53 AM, Nikhila, Athaluri (Nokia - IN/Bangalore)
> <athaluri.nikhila@nokia.com> wrote:
>
> Hi,
>
>      I am trying to run the kni application which is an example of DPDK
> and I am getting the following error. Can anyone please help me out.
>
> Hugepages - 303 hugepages (2 MB)
> Error: exiting with code 1
>  Cause : could not initialize mbuf pool.
>
> Thanks in advance.
>
>
> sudo ./build/app/kni -c 0xf -n 4 -- -P -p 0x3 --config="(0,0,1),(1,2,3)"
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 4 lcore(s)
> EAL: Setting up physically contiguous memory...
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7f0ee1600000 (size = 0x600000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ee1200000 (size = 0x200000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7f0ee0c00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ee0800000 (size = 0x200000)
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7f0ee0000000 (size = 0x600000)
> EAL: Ask a virtual area of 0x4800000 bytes
> EAL: Virtual area found at 0x7f0edb600000 (size = 0x4800000)
> EAL: Ask a virtual area of 0x4c00000 bytes
> EAL: Virtual area found at 0x7f0ed6800000 (size = 0x4c00000)
> EAL: Ask a virtual area of 0x1e00000 bytes
> EAL: Virtual area found at 0x7f0ed4800000 (size = 0x1e00000)
> EAL: Ask a virtual area of 0xc00000 bytes
> EAL: Virtual area found at 0x7f0ed3a00000 (size = 0xc00000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ed3600000 (size = 0x200000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ed3200000 (size = 0x200000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7f0ed2c00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7f0ed2400000 (size = 0x600000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ed2000000 (size = 0x200000)
> EAL: Ask a virtual area of 0x800000 bytes
> EAL: Virtual area found at 0x7f0ed1600000 (size = 0x800000)
> EAL: Ask a virtual area of 0x800000 bytes
> EAL: Virtual area found at 0x7f0ed0c00000 (size = 0x800000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ed0800000 (size = 0x200000)
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7f0ed0000000 (size = 0x600000)
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7f0ecf800000 (size = 0x600000)
> EAL: Ask a virtual area of 0x1c00000 bytes
> EAL: Virtual area found at 0x7f0ecda00000 (size = 0x1c00000)
> EAL: Ask a virtual area of 0x2800000 bytes
> EAL: Virtual area found at 0x7f0ecb000000 (size = 0x2800000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ecac00000 (size = 0x200000)
> EAL: Ask a virtual area of 0x4600000 bytes
> EAL: Virtual area found at 0x7f0ec6400000 (size = 0x4600000)
> EAL: Ask a virtual area of 0x1c00000 bytes
> EAL: Virtual area found at 0x7f0ec4600000 (size = 0x1c00000)
> EAL: Ask a virtual area of 0xe00000 bytes
> EAL: Virtual area found at 0x7f0ec3600000 (size = 0xe00000)
> EAL: Ask a virtual area of 0x2000000 bytes
> EAL: Virtual area found at 0x7f0ec1400000 (size = 0x2000000)
> EAL: Ask a virtual area of 0x1200000 bytes
> EAL: Virtual area found at 0x7f0ec0000000 (size = 0x1200000)
> EAL: Ask a virtual area of 0x1000000 bytes
> EAL: Virtual area found at 0x7f0ebee00000 (size = 0x1000000)
> EAL: Ask a virtual area of 0xa00000 bytes
> EAL: Virtual area found at 0x7f0ebe200000 (size = 0xa00000)
> EAL: Ask a virtual area of 0x600000 bytes
> EAL: Virtual area found at 0x7f0ebda00000 (size = 0x600000)
> EAL: Ask a virtual area of 0xa00000 bytes
> EAL: Virtual area found at 0x7f0ebce00000 (size = 0xa00000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0ebca00000 (size = 0x200000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7f0ebc400000 (size = 0x400000)
> EAL: Ask a virtual area of 0x1400000 bytes
> EAL: Virtual area found at 0x7f0ebae00000 (size = 0x1400000)
> EAL: Ask a virtual area of 0x800000 bytes
> EAL: Virtual area found at 0x7f0eba400000 (size = 0x800000)
> EAL: Ask a virtual area of 0x800000 bytes
> EAL: Virtual area found at 0x7f0eb9a00000 (size = 0x800000)
> EAL: Ask a virtual area of 0xc00000 bytes
> EAL: Virtual area found at 0x7f0eb8c00000 (size = 0xc00000)
> EAL: Ask a virtual area of 0x1000000 bytes
> EAL: Virtual area found at 0x7f0eb7a00000 (size = 0x1000000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0eb7600000 (size = 0x200000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0eb7200000 (size = 0x200000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f0eb6e00000 (size = 0x200000)
> EAL: Requesting 303 pages of size 2MB from socket 0
> EAL: TSC frequency is ~2690619 KHz
> EAL: Master lcore 0 is ready (tid=e428f900;cpuset=[0])
> EAL: lcore 3 is ready (tid=b5dfd700;cpuset=[3])
> EAL: lcore 1 is ready (tid=b6dff700;cpuset=[1])
> EAL: lcore 2 is ready (tid=b65fe700;cpuset=[2])
> EAL: PCI device 0000:00:03.0 on NUMA socket -1
> EAL:   probe driver: 8086:100e rte_em_pmd
> EAL:   PCI memory mapped at 0x7f0ee1c00000
> PMD: eth_em_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x100e
> EAL: PCI device 0000:00:08.0 on NUMA socket -1
> EAL:   probe driver: 8086:100e rte_em_pmd
> EAL:   PCI memory mapped at 0x7f0ee1c20000
> PMD: eth_em_dev_init(): port_id 1 vendorID=0x8086 deviceID=0x100e
> EAL: PCI device 0000:00:09.0 on NUMA socket -1
> EAL:   probe driver: 8086:100e rte_em_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:00:0a.0 on NUMA socket -1
> EAL:   probe driver: 8086:100e rte_em_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> APP: Port ID: 0
> APP: Rx lcore ID: 0, Tx lcore ID: 1
> APP: Port ID: 1
> APP: Rx lcore ID: 2, Tx lcore ID: 3
> EAL: Error - exiting with code: 1
>   Cause: Could not initialise mbuf pool
>
>
>

[dpdk-users] Issue on Running KNI application

[P D, Arun (Nokia - IN/Bangalore)]

Hello,

I am trying to run the KNI program in examples of dpdk.

I am giving the following command and facing the error as  "Cause: lcore id 1 for port 0 receiving not enabled".

Please let me know if I am making any mistake at config parameters, or I am missing something.

./kni -c 4 -n 4 -- -P -p 0x3 --config="(0,1,3),(1,2,4)"

EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fd603600000 (size = 0x200000)
EAL: Ask a virtual area of 0x1000000 bytes
EAL: Virtual area found at 0x7fd602400000 (size = 0x1000000)
EAL: Ask a virtual area of 0x3c00000 bytes
EAL: Virtual area found at 0x7fd5fe600000 (size = 0x3c00000)
EAL: Ask a virtual area of 0x50400000 bytes
EAL: Virtual area found at 0x7fd5ae000000 (size = 0x50400000)
EAL: Ask a virtual area of 0x29c00000 bytes
EAL: Virtual area found at 0x7fd584200000 (size = 0x29c00000)
EAL: Ask a virtual area of 0x1000000 bytes
EAL: Virtual area found at 0x7fd583000000 (size = 0x1000000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fd582c00000 (size = 0x200000)
EAL: Requesting 1024 pages of size 2MB from socket 0
EAL: TSC frequency is ~3192614 KHz
EAL: Master lcore 2 is ready (tid=3cb98e0;cpuset=[2])
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL:   probe driver: 8086:1533 rte_igb_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:05:00.0 on NUMA socket -1
EAL:   probe driver: 8086:100e rte_em_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:06:00.0 on NUMA socket -1
EAL:   probe driver: 8086:10d3 rte_em_pmd
EAL:   Not managed by a supported kernel driver, skipped
APP: Port ID: 0
APP: Rx lcore ID: 1, Tx lcore ID: 3
APP: Port ID: 1
APP: Rx lcore ID: 2, Tx lcore ID: 4
EAL: Error - exiting with code: 1
  Cause: lcore id 1 for port 0 receiving not enabled

Regards,
Arun Raj

Re: [dpdk-users] Issue on Running KNI application

[Ilir Iljazi]

I've come across this issue also with a Realtek network card. The driver your device uses is incompatible with dpdk. Currently only Intel cards are supported, to the best of my knowledge. 

EAL:   Not managed by a supported kernel driver, skipped

What type of nic do you have:

#lspci | grep -i ether

Ilir

> On Dec 8, 2015, at 12:05 PM, P D, Arun (Nokia - IN/Bangalore) <arun.p_d@nokia.com> wrote:
> 
> EAL:   Not managed by a supported kernel driver, skipped

Re: [dpdk-users] Issue on Running KNI application

[Pattan, Reshma]

Hi Arun,

Core mask value i.e. -c value should be 0x1E in your command. Because you are using cores 1,2,3,4 so their respective bits must be set to 1 in -c value.

./kni -c 0x1E -n 4 -- -P -p 0x3 --config="(0,1,3),(1,2,4)"

Thanks,
Reshma

> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of P D, Arun (Nokia -
> IN/Bangalore)
> Sent: Tuesday, December 8, 2015 6:06 PM
> To: users@dpdk.org
> Subject: [dpdk-users] Issue on Running KNI application
> 
> Hello,
> 
> I am trying to run the KNI program in examples of dpdk.
> 
> I am giving the following command and facing the error as  "Cause: lcore id 1 for
> port 0 receiving not enabled".
> 
> Please let me know if I am making any mistake at config parameters, or I am
> missing something.
> 
> ./kni -c 4 -n 4 -- -P -p 0x3 --config="(0,1,3),(1,2,4)"
> 
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 4 lcore(s)
> EAL: Setting up physically contiguous memory...
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7fd603600000 (size = 0x200000)
> EAL: Ask a virtual area of 0x1000000 bytes
> EAL: Virtual area found at 0x7fd602400000 (size = 0x1000000)
> EAL: Ask a virtual area of 0x3c00000 bytes
> EAL: Virtual area found at 0x7fd5fe600000 (size = 0x3c00000)
> EAL: Ask a virtual area of 0x50400000 bytes
> EAL: Virtual area found at 0x7fd5ae000000 (size = 0x50400000)
> EAL: Ask a virtual area of 0x29c00000 bytes
> EAL: Virtual area found at 0x7fd584200000 (size = 0x29c00000)
> EAL: Ask a virtual area of 0x1000000 bytes
> EAL: Virtual area found at 0x7fd583000000 (size = 0x1000000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7fd582c00000 (size = 0x200000)
> EAL: Requesting 1024 pages of size 2MB from socket 0
> EAL: TSC frequency is ~3192614 KHz
> EAL: Master lcore 2 is ready (tid=3cb98e0;cpuset=[2])
> EAL: PCI device 0000:03:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:1533 rte_igb_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:05:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:100e rte_em_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:06:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:10d3 rte_em_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> APP: Port ID: 0
> APP: Rx lcore ID: 1, Tx lcore ID: 3
> APP: Port ID: 1
> APP: Rx lcore ID: 2, Tx lcore ID: 4
> EAL: Error - exiting with code: 1
>   Cause: lcore id 1 for port 0 receiving not enabled
> 
> Regards,
> Arun Raj

Re: [dpdk-users] Issue on Running KNI application

[P D, Arun (Nokia - IN/Bangalore)]

Hi Reshma,

I am getting error, upon executing saying that it's an invalid core mask.

Also please let me know how you are calculating the hexadecimal bitmask for the cores.

./kni -c 0x1E -n 4 -- -P -p 0x3 --config="(0,1,3),(1,2,4)"

EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 4 lcore(s)
EAL: lcore 4 unavailable
EAL: invalid coremask

Regards,
Arun Raj

-----Original Message-----
From: EXT Pattan, Reshma [mailto:reshma.pattan@intel.com] 
Sent: Wednesday, December 09, 2015 3:37 AM
To: P D, Arun (Nokia - IN/Bangalore) <arun.p_d@nokia.com>; users@dpdk.org
Subject: RE: Issue on Running KNI application

Hi Arun,

Core mask value i.e. -c value should be 0x1E in your command. Because you are using cores 1,2,3,4 so their respective bits must be set to 1 in -c value.

./kni -c 0x1E -n 4 -- -P -p 0x3 --config="(0,1,3),(1,2,4)"

Thanks,
Reshma

> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of P D, Arun (Nokia -
> IN/Bangalore)
> Sent: Tuesday, December 8, 2015 6:06 PM
> To: users@dpdk.org
> Subject: [dpdk-users] Issue on Running KNI application
> 
> Hello,
> 
> I am trying to run the KNI program in examples of dpdk.
> 
> I am giving the following command and facing the error as  "Cause: lcore id 1 for
> port 0 receiving not enabled".
> 
> Please let me know if I am making any mistake at config parameters, or I am
> missing something.
> 
> ./kni -c 4 -n 4 -- -P -p 0x3 --config="(0,1,3),(1,2,4)"
> 
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 4 lcore(s)
> EAL: Setting up physically contiguous memory...
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7fd603600000 (size = 0x200000)
> EAL: Ask a virtual area of 0x1000000 bytes
> EAL: Virtual area found at 0x7fd602400000 (size = 0x1000000)
> EAL: Ask a virtual area of 0x3c00000 bytes
> EAL: Virtual area found at 0x7fd5fe600000 (size = 0x3c00000)
> EAL: Ask a virtual area of 0x50400000 bytes
> EAL: Virtual area found at 0x7fd5ae000000 (size = 0x50400000)
> EAL: Ask a virtual area of 0x29c00000 bytes
> EAL: Virtual area found at 0x7fd584200000 (size = 0x29c00000)
> EAL: Ask a virtual area of 0x1000000 bytes
> EAL: Virtual area found at 0x7fd583000000 (size = 0x1000000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7fd582c00000 (size = 0x200000)
> EAL: Requesting 1024 pages of size 2MB from socket 0
> EAL: TSC frequency is ~3192614 KHz
> EAL: Master lcore 2 is ready (tid=3cb98e0;cpuset=[2])
> EAL: PCI device 0000:03:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:1533 rte_igb_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:05:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:100e rte_em_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> EAL: PCI device 0000:06:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:10d3 rte_em_pmd
> EAL:   Not managed by a supported kernel driver, skipped
> APP: Port ID: 0
> APP: Rx lcore ID: 1, Tx lcore ID: 3
> APP: Port ID: 1
> APP: Rx lcore ID: 2, Tx lcore ID: 4
> EAL: Error - exiting with code: 1
>   Cause: lcore id 1 for port 0 receiving not enabled
> 
> Regards,
> Arun Raj

Re: [dpdk-users] Issue on Running KNI application

[Pattan, Reshma]

Hi Arun,

I see below EAL info from the given output, that means you have only 4 lcores on your board numbering 0, 1,2,3.
So you need to change the core mask and core numbering that you have passed  to --config.

> EAL: Detected 4 lcore(s)
> EAL: lcore 4 unavailable

Ex: if you want to use all 4 cores u need to try below command
 ./kni -c 0xf -n 4 -- -P -p 0x3 --config="(0,1,0),(1,2,3)"

-c 0xf 				==> enables all 4 cores 0,1,2,3
--config="(0,1,0),(1,2,3)" 	==>(0,1,0) core 1 is RX core and core 0 is TX core
				==>(1,2,3) core 2 is RX core and core 3 is TX core

You can change RX and TX core numbers to your choice,  I just gave an example. 
But whatever cores you wants to use make sure those exists on board and should be enabled in core mask and the same should be used in config option.
You can check how many lcores are there on your board by using ./too/cpu_layout.py

To check how to run KNI and understand command line options  take a look at KNI sample application section from Sample Application User guide.

Thanks,
Reshma

> -----Original Message-----
> From: P D, Arun (Nokia - IN/Bangalore) [mailto:arun.p_d@nokia.com]
> Sent: Wednesday, December 9, 2015 5:49 AM
> To: Pattan, Reshma
> Cc: users@dpdk.org
> Subject: RE: Issue on Running KNI application
> 
> Hi Reshma,
> 
> I am getting error, upon executing saying that it's an invalid core mask.
> 
> Also please let me know how you are calculating the hexadecimal bitmask for
> the cores.
> 
> ./kni -c 0x1E -n 4 -- -P -p 0x3 --config="(0,1,3),(1,2,4)"
> 
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 4 lcore(s)
> EAL: lcore 4 unavailable
> EAL: invalid coremask
> 
> Regards,
> Arun Raj
> 
> -----Original Message-----
> From: EXT Pattan, Reshma [mailto:reshma.pattan@intel.com]
> Sent: Wednesday, December 09, 2015 3:37 AM
> To: P D, Arun (Nokia - IN/Bangalore) <arun.p_d@nokia.com>; users@dpdk.org
> Subject: RE: Issue on Running KNI application
> 
> Hi Arun,
> 
> Core mask value i.e. -c value should be 0x1E in your command. Because you are
> using cores 1,2,3,4 so their respective bits must be set to 1 in -c value.
> 
> ./kni -c 0x1E -n 4 -- -P -p 0x3 --config="(0,1,3),(1,2,4)"
> 
> Thanks,
> Reshma
> 
> > -----Original Message-----
> > From: users [mailto:users-bounces@dpdk.org] On Behalf Of P D, Arun
> > (Nokia -
> > IN/Bangalore)
> > Sent: Tuesday, December 8, 2015 6:06 PM
> > To: users@dpdk.org
> > Subject: [dpdk-users] Issue on Running KNI application
> >
> > Hello,
> >
> > I am trying to run the KNI program in examples of dpdk.
> >
> > I am giving the following command and facing the error as  "Cause:
> > lcore id 1 for port 0 receiving not enabled".
> >
> > Please let me know if I am making any mistake at config parameters, or
> > I am missing something.
> >
> > ./kni -c 4 -n 4 -- -P -p 0x3 --config="(0,1,3),(1,2,4)"
> >
> > EAL: Detected lcore 0 as core 0 on socket 0
> > EAL: Detected lcore 1 as core 1 on socket 0
> > EAL: Detected lcore 2 as core 2 on socket 0
> > EAL: Detected lcore 3 as core 3 on socket 0
> > EAL: Support maximum 128 logical core(s) by configuration.
> > EAL: Detected 4 lcore(s)
> > EAL: Setting up physically contiguous memory...
> > EAL: Ask a virtual area of 0x200000 bytes
> > EAL: Virtual area found at 0x7fd603600000 (size = 0x200000)
> > EAL: Ask a virtual area of 0x1000000 bytes
> > EAL: Virtual area found at 0x7fd602400000 (size = 0x1000000)
> > EAL: Ask a virtual area of 0x3c00000 bytes
> > EAL: Virtual area found at 0x7fd5fe600000 (size = 0x3c00000)
> > EAL: Ask a virtual area of 0x50400000 bytes
> > EAL: Virtual area found at 0x7fd5ae000000 (size = 0x50400000)
> > EAL: Ask a virtual area of 0x29c00000 bytes
> > EAL: Virtual area found at 0x7fd584200000 (size = 0x29c00000)
> > EAL: Ask a virtual area of 0x1000000 bytes
> > EAL: Virtual area found at 0x7fd583000000 (size = 0x1000000)
> > EAL: Ask a virtual area of 0x200000 bytes
> > EAL: Virtual area found at 0x7fd582c00000 (size = 0x200000)
> > EAL: Requesting 1024 pages of size 2MB from socket 0
> > EAL: TSC frequency is ~3192614 KHz
> > EAL: Master lcore 2 is ready (tid=3cb98e0;cpuset=[2])
> > EAL: PCI device 0000:03:00.0 on NUMA socket -1
> > EAL:   probe driver: 8086:1533 rte_igb_pmd
> > EAL:   Not managed by a supported kernel driver, skipped
> > EAL: PCI device 0000:05:00.0 on NUMA socket -1
> > EAL:   probe driver: 8086:100e rte_em_pmd
> > EAL:   Not managed by a supported kernel driver, skipped
> > EAL: PCI device 0000:06:00.0 on NUMA socket -1
> > EAL:   probe driver: 8086:10d3 rte_em_pmd
> > EAL:   Not managed by a supported kernel driver, skipped
> > APP: Port ID: 0
> > APP: Rx lcore ID: 1, Tx lcore ID: 3
> > APP: Port ID: 1
> > APP: Rx lcore ID: 2, Tx lcore ID: 4
> > EAL: Error - exiting with code: 1
> >   Cause: lcore id 1 for port 0 receiving not enabled
> >
> > Regards,
> > Arun Raj

Re: [dpdk-users] Issue on Running KNI application

[P D, Arun (Nokia - IN/Bangalore)]

Thanks for your inputs.

Regards,
Arun Raj

-----Original Message-----
From: EXT Pattan, Reshma [mailto:reshma.pattan@intel.com] 
Sent: Wednesday, December 09, 2015 5:12 PM
To: P D, Arun (Nokia - IN/Bangalore) <arun.p_d@nokia.com>
Cc: users@dpdk.org
Subject: RE: Issue on Running KNI application

Hi Arun,

I see below EAL info from the given output, that means you have only 4 lcores on your board numbering 0, 1,2,3.
So you need to change the core mask and core numbering that you have passed  to --config.

> EAL: Detected 4 lcore(s)
> EAL: lcore 4 unavailable

Ex: if you want to use all 4 cores u need to try below command
 ./kni -c 0xf -n 4 -- -P -p 0x3 --config="(0,1,0),(1,2,3)"

-c 0xf 				==> enables all 4 cores 0,1,2,3
--config="(0,1,0),(1,2,3)" 	==>(0,1,0) core 1 is RX core and core 0 is TX core
				==>(1,2,3) core 2 is RX core and core 3 is TX core

You can change RX and TX core numbers to your choice,  I just gave an example. 
But whatever cores you wants to use make sure those exists on board and should be enabled in core mask and the same should be used in config option.
You can check how many lcores are there on your board by using ./too/cpu_layout.py

To check how to run KNI and understand command line options  take a look at KNI sample application section from Sample Application User guide.

Thanks,
Reshma

> -----Original Message-----
> From: P D, Arun (Nokia - IN/Bangalore) [mailto:arun.p_d@nokia.com]
> Sent: Wednesday, December 9, 2015 5:49 AM
> To: Pattan, Reshma
> Cc: users@dpdk.org
> Subject: RE: Issue on Running KNI application
> 
> Hi Reshma,
> 
> I am getting error, upon executing saying that it's an invalid core mask.
> 
> Also please let me know how you are calculating the hexadecimal bitmask for
> the cores.
> 
> ./kni -c 0x1E -n 4 -- -P -p 0x3 --config="(0,1,3),(1,2,4)"
> 
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Support maximum 128 logical core(s) by configuration.
> EAL: Detected 4 lcore(s)
> EAL: lcore 4 unavailable
> EAL: invalid coremask
> 
> Regards,
> Arun Raj
> 
> -----Original Message-----
> From: EXT Pattan, Reshma [mailto:reshma.pattan@intel.com]
> Sent: Wednesday, December 09, 2015 3:37 AM
> To: P D, Arun (Nokia - IN/Bangalore) <arun.p_d@nokia.com>; users@dpdk.org
> Subject: RE: Issue on Running KNI application
> 
> Hi Arun,
> 
> Core mask value i.e. -c value should be 0x1E in your command. Because you are
> using cores 1,2,3,4 so their respective bits must be set to 1 in -c value.
> 
> ./kni -c 0x1E -n 4 -- -P -p 0x3 --config="(0,1,3),(1,2,4)"
> 
> Thanks,
> Reshma
> 
> > -----Original Message-----
> > From: users [mailto:users-bounces@dpdk.org] On Behalf Of P D, Arun
> > (Nokia -
> > IN/Bangalore)
> > Sent: Tuesday, December 8, 2015 6:06 PM
> > To: users@dpdk.org
> > Subject: [dpdk-users] Issue on Running KNI application
> >
> > Hello,
> >
> > I am trying to run the KNI program in examples of dpdk.
> >
> > I am giving the following command and facing the error as  "Cause:
> > lcore id 1 for port 0 receiving not enabled".
> >
> > Please let me know if I am making any mistake at config parameters, or
> > I am missing something.
> >
> > ./kni -c 4 -n 4 -- -P -p 0x3 --config="(0,1,3),(1,2,4)"
> >
> > EAL: Detected lcore 0 as core 0 on socket 0
> > EAL: Detected lcore 1 as core 1 on socket 0
> > EAL: Detected lcore 2 as core 2 on socket 0
> > EAL: Detected lcore 3 as core 3 on socket 0
> > EAL: Support maximum 128 logical core(s) by configuration.
> > EAL: Detected 4 lcore(s)
> > EAL: Setting up physically contiguous memory...
> > EAL: Ask a virtual area of 0x200000 bytes
> > EAL: Virtual area found at 0x7fd603600000 (size = 0x200000)
> > EAL: Ask a virtual area of 0x1000000 bytes
> > EAL: Virtual area found at 0x7fd602400000 (size = 0x1000000)
> > EAL: Ask a virtual area of 0x3c00000 bytes
> > EAL: Virtual area found at 0x7fd5fe600000 (size = 0x3c00000)
> > EAL: Ask a virtual area of 0x50400000 bytes
> > EAL: Virtual area found at 0x7fd5ae000000 (size = 0x50400000)
> > EAL: Ask a virtual area of 0x29c00000 bytes
> > EAL: Virtual area found at 0x7fd584200000 (size = 0x29c00000)
> > EAL: Ask a virtual area of 0x1000000 bytes
> > EAL: Virtual area found at 0x7fd583000000 (size = 0x1000000)
> > EAL: Ask a virtual area of 0x200000 bytes
> > EAL: Virtual area found at 0x7fd582c00000 (size = 0x200000)
> > EAL: Requesting 1024 pages of size 2MB from socket 0
> > EAL: TSC frequency is ~3192614 KHz
> > EAL: Master lcore 2 is ready (tid=3cb98e0;cpuset=[2])
> > EAL: PCI device 0000:03:00.0 on NUMA socket -1
> > EAL:   probe driver: 8086:1533 rte_igb_pmd
> > EAL:   Not managed by a supported kernel driver, skipped
> > EAL: PCI device 0000:05:00.0 on NUMA socket -1
> > EAL:   probe driver: 8086:100e rte_em_pmd
> > EAL:   Not managed by a supported kernel driver, skipped
> > EAL: PCI device 0000:06:00.0 on NUMA socket -1
> > EAL:   probe driver: 8086:10d3 rte_em_pmd
> > EAL:   Not managed by a supported kernel driver, skipped
> > APP: Port ID: 0
> > APP: Rx lcore ID: 1, Tx lcore ID: 3
> > APP: Port ID: 1
> > APP: Rx lcore ID: 2, Tx lcore ID: 4
> > EAL: Error - exiting with code: 1
> >   Cause: lcore id 1 for port 0 receiving not enabled
> >
> > Regards,
> > Arun Raj