DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Abdul, Jaffar" <jabdul@ciena.com>
To: Nishant Verma <vnish11@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Ismail, Aws" <aismail@ciena.com>
Subject: Re: [dpdk-dev] KNI sample application running procedure
Date: Mon, 7 Dec 2015 17:50:05 -0500	[thread overview]
Message-ID: <23903483D1A9B04AB5D759C6C845237F043A363A6A@ONWVEXCHMB05.ciena.com> (raw)
In-Reply-To: <CAHhCjUE1GfOzmxw=fTFyEpO8Xdb8aop22g42h1U1usHXZhZv5Q@mail.gmail.com>

Hi Nishant,

Thanks for your suggestions but even it did not work, In the meanwhile, I will see what can I do from my side. Any other suggestions from the community is also really helpful at this time

root@x10sdv-f:/opt/dpdk/x86_64-native-linuxapp-gcc/app# ./kni -c 0x0f -n 2 -- -P -p 0x3 --config="(0,2,3),(1,0,1)"
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: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 6 on socket 0
EAL: Detected lcore 7 as core 7 on socket 0
EAL: Detected lcore 8 as core 0 on socket 0
EAL: Detected lcore 9 as core 1 on socket 0
EAL: Detected lcore 10 as core 2 on socket 0
EAL: Detected lcore 11 as core 3 on socket 0
EAL: Detected lcore 12 as core 4 on socket 0
EAL: Detected lcore 13 as core 5 on socket 0
EAL: Detected lcore 14 as core 6 on socket 0
EAL: Detected lcore 15 as core 7 on socket 0
EAL: Support maximum 16 logical core(s) by configuration.
EAL: Detected 16 lcore(s)
EAL: VFIO modules not all loaded, skip VFIO support...
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7ff6be400000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7ff6be000000 (size = 0x200000)
EAL: Ask a virtual area of 0x3c400000 bytes
EAL: Virtual area found at 0x7ff681a00000 (size = 0x3c400000)
EAL: Ask a virtual area of 0x3600000 bytes
EAL: Virtual area found at 0x7ff67e200000 (size = 0x3600000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7ff67de00000 (size = 0x200000)
EAL: Ask a virtual area of 0xc0000000 bytes
EAL: Virtual area found at 0x7ff5bdc00000 (size = 0xc0000000)
EAL: Requesting 2048 pages of size 2MB from socket 0
EAL: TSC frequency is ~2000001 KHz
EAL: Master lcore 0 is ready (tid=bf8028c0;cpuset=[0])
EAL: lcore 3 is ready (tid=bcbfd700;cpuset=[3])
EAL: lcore 1 is ready (tid=bdbff700;cpuset=[1])
EAL: lcore 2 is ready (tid=bd3fe700;cpuset=[2])
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL:   probe driver: 8086:15ad rte_ixgbe_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:03:00.1 on NUMA socket -1
EAL:   probe driver: 8086:15ad rte_ixgbe_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:1521 rte_igb_pmd
EAL:   PCI memory mapped at 0x7ff6be600000
EAL:   PCI memory mapped at 0x7ff6be620000
PMD: eth_igb_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x1521
EAL: PCI device 0000:05:00.1 on NUMA socket -1
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   PCI memory mapped at 0x7ff6be624000
EAL:   PCI memory mapped at 0x7ff6be644000
PMD: eth_igb_dev_init(): port_id 1 vendorID=0x8086 deviceID=0x1521
APP: Port ID: 0
APP: Rx lcore ID: 2, Tx lcore ID: 3
APP: Port ID: 1
APP: Rx lcore ID: 0, Tx lcore ID: 1
EAL: Error - exiting with code: 1
  Cause: portmask is not consistent to port ids specified in --config
root@x10sdv-f:/opt/dpdk/x86_64-native-linuxapp-gcc/app#

Thanks
Jaffar

From: Nishant Verma [mailto:vnish11@gmail.com]
Sent: Monday, December 07, 2015 1:58 PM
To: Abdul, Jaffar
Cc: dev@dpdk.org; Ismail, Aws
Subject: Re: [dpdk-dev] KNI sample application running procedure

As par error message, it seems error lies in validation. But it seems right
Can you try to run the app without kthread option. if you haven't tried that. just to pin point the problem.

./kni -c 0x0f -n 2 -- -P -p 0x3 --config="(0,2,3),(1,0,1)"
while executing, load kni module with single mode option.


On Mon, Dec 7, 2015 at 3:48 PM, Abdul, Jaffar <jabdul@ciena.com<mailto:jabdul@ciena.com>> wrote:
Hi Guys,

I am trying to run the KNI sample application according to the DPDK documentation which is given below.

http://dpdk.org/doc/guides/sample_app_ug/kernel_nic_interface.html#running-the-application

I am not able to run the app successfully,

I don't have this problem with any other DPDK example application and I also verified that I have loaded the *.ko files properly (rte_kni.ko, igb_uio.ko, etc.)

I have also loaded rte_kni.ko with kthread_mode single/multiple but both results are same.

I am using two 1G ports in this example which are port 0 and port 1 and it has been attached to DPDK through (dpdk_nic_bind.py) script.

Output of the dpdk_nic_bind.py
========================
root@x10sdv-f:/# /opt/dpdk/tools/dpdk_nic_bind.py --status

Network devices using DPDK-compatible driver
============================================
0000:05:00.0 'I350 Gigabit Network Connection' drv=igb_uio unused=
0000:05:00.1 'I350 Gigabit Network Connection' drv=igb_uio unused=

Network devices using kernel driver
===================================
0000:03:00.0 'Device 15ad' if=eth2 drv=ixgbe unused=igb_uio
0000:03:00.1 'Device 15ad' if=eth3 drv=ixgbe unused=igb_uio

Other network devices
=====================
<none>

Here is how I am loading the KNI sample application
========================================
root@x10sdv-f:/opt/dpdk/x86_64-native-linuxapp-gcc/app# ./kni -c 0x0f -n 2 -- -P -p 0x3 --config="(0,2,3,0),(1,0,1,0)"
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: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 6 on socket 0
EAL: Detected lcore 7 as core 7 on socket 0
EAL: Detected lcore 8 as core 0 on socket 0
EAL: Detected lcore 9 as core 1 on socket 0
EAL: Detected lcore 10 as core 2 on socket 0
EAL: Detected lcore 11 as core 3 on socket 0
EAL: Detected lcore 12 as core 4 on socket 0
EAL: Detected lcore 13 as core 5 on socket 0
EAL: Detected lcore 14 as core 6 on socket 0
EAL: Detected lcore 15 as core 7 on socket 0
EAL: Support maximum 16 logical core(s) by configuration.
EAL: Detected 16 lcore(s)
EAL: VFIO modules not all loaded, skip VFIO support...
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fa274600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fa274200000 (size = 0x200000)
EAL: Ask a virtual area of 0x3c400000 bytes
EAL: Virtual area found at 0x7fa237c00000 (size = 0x3c400000)
EAL: Ask a virtual area of 0x3600000 bytes
EAL: Virtual area found at 0x7fa234400000 (size = 0x3600000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fa234000000 (size = 0x200000)
EAL: Ask a virtual area of 0xc0000000 bytes
EAL: Virtual area found at 0x7fa173e00000 (size = 0xc0000000)
EAL: Requesting 2048 pages of size 2MB from socket 0
EAL: TSC frequency is ~2000001 KHz
EAL: Master lcore 0 is ready (tid=75a328c0;cpuset=[0])
EAL: lcore 3 is ready (tid=72dfd700;cpuset=[3])
EAL: lcore 1 is ready (tid=73dff700;cpuset=[1])
EAL: lcore 2 is ready (tid=735fe700;cpuset=[2])
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL:   probe driver: 8086:15ad rte_ixgbe_pmd
EAL:   Not managed by a supported kernel driver, skipped
EAL: PCI device 0000:03:00.1 on NUMA socket -1
EAL:   probe driver: 8086:15ad rte_ixgbe_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:1521 rte_igb_pmd
EAL:   PCI memory mapped at 0x7fa274800000
EAL:   PCI memory mapped at 0x7fa274820000
PMD: eth_igb_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x1521
EAL: PCI device 0000:05:00.1 on NUMA socket -1
EAL:   probe driver: 8086:1521 rte_igb_pmd
EAL:   PCI memory mapped at 0x7fa274824000
EAL:   PCI memory mapped at 0x7fa274844000
PMD: eth_igb_dev_init(): port_id 1 vendorID=0x8086 deviceID=0x1521
APP: Port ID: 0
APP: Rx lcore ID: 2, Tx lcore ID: 3
APP: Kernel thread lcore ID: 0
APP: Port ID: 1
APP: Rx lcore ID: 0, Tx lcore ID: 1
APP: Kernel thread lcore ID: 0
EAL: Error - exiting with code: 1
  Cause: portmask is not consistent to port ids specified in --config
root@x10sdv-f:/opt/dpdk/x86_64-native-linuxapp-gcc/app#



we are using dpdk v2.1 at this moment, any suggestions to make this work would be a great help for me.

Please let me know if you need more info on this

Thanks a lot in advance!

Thanks
Jaffar



--
Rgds,
Nishant



      reply	other threads:[~2015-12-07 22:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07 20:48 Abdul, Jaffar
2015-12-07 21:57 ` Nishant Verma
2015-12-07 22:50   ` Abdul, Jaffar [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=23903483D1A9B04AB5D759C6C845237F043A363A6A@ONWVEXCHMB05.ciena.com \
    --to=jabdul@ciena.com \
    --cc=aismail@ciena.com \
    --cc=dev@dpdk.org \
    --cc=vnish11@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).