From: Murali Krishna <murali.krishna@broadcom.com>
To: Vladimir Medvedkin <medvedkinv@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] unable to run l2fwd application due to 'Cause: No Ethernet ports - bye' error
Date: Fri, 18 Mar 2016 21:16:02 +0530 [thread overview]
Message-ID: <b8c56169bd576074835cf3baefb9df19@mail.gmail.com> (raw)
In-Reply-To: 053ac883dac86a16b8c63962ab0ef6f6@mail.gmail.com
[root@Rhel67GA-Valencia drivers]# python /dpdk-2.0.0/tools/dpdk_nic_bind.py
--status
Network devices using DPDK-compatible driver
============================================
<none>
Network devices using kernel driver
===================================
0000:01:00.2 'OneConnect NIC (Skyhawk)' if=em3 drv=be2net unused=
0000:01:00.3 'OneConnect NIC (Skyhawk)' if=em4 drv=be2net unused=
0000:82:00.0 'OneConnect NIC (Skyhawk)' if=p1p1 drv=be2net unused=
0000:82:00.1 'OneConnect NIC (Skyhawk)' if=p1p2 drv=be2net unused=
0000:82:00.2 'OneConnect NIC (Skyhawk)' if=p1p3 drv=be2net unused=
0000:82:00.3 'OneConnect NIC (Skyhawk)' if=p1p4 drv=be2net unused=
0000:82:00.4 'OneConnect NIC (Skyhawk)' if=p1p5 drv=be2net unused=
0000:82:00.5 'OneConnect NIC (Skyhawk)' if=p1p6 drv=be2net unused=
0000:82:00.6 'OneConnect NIC (Skyhawk)' if=p1p7 drv=be2net unused=
0000:82:00.7 'OneConnect NIC (Skyhawk)' if=p1p8 drv=be2net unused=
Other network devices
=====================
0000:01:00.0 'OneConnect NIC (Skyhawk)' unused=be2net
0000:01:00.1 'OneConnect NIC (Skyhawk)' unused=be2net
*From:* Murali Krishna [mailto:murali.krishna@broadcom.com]
*Sent:* Friday, March 18, 2016 8:56 PM
*To:* 'Vladimir Medvedkin'
*Cc:* 'users@dpdk.org'
*Subject:* RE: [dpdk-users] unable to run l2fwd application due to 'Cause:
No Ethernet ports - bye' error
Hi Vladimir,
Attached dpdk-2.0.0/tools/dpdk_nic_bind.py file. Let me know if you are not
able to open the attachment.
Thanks,
Murali
*From:* Vladimir Medvedkin [mailto:medvedkinv@gmail.com]
*Sent:* Friday, March 18, 2016 8:51 PM
*To:* Murali Krishna
*Cc:* users@dpdk.org
*Subject:* Re: [dpdk-users] unable to run l2fwd application due to 'Cause:
No Ethernet ports - bye' error
Hi,
Show tools/dpdk_nic_bind.py --status
Regards,
Vladimir
2016-03-18 18:11 GMT+03:00 Murali Krishna <murali.krishna@broadcom.com>:
Hi All,
I am unable to run l2fwd app on linux, due to ‘Cause: No Ethernet ports -
bye' error
I am using *DPDK 2.0.0* with *Emulex OCe14102* adapter
[root@Rhel67GA-Valencia DPDK2]# lspci | grep Emulex
01:00.0 Ethernet controller: Emulex Corporation OneConnect NIC (Skyhawk)
(rev 10)
01:00.1 Ethernet controller: Emulex Corporation OneConnect NIC (Skyhawk)
(rev 10)
The Emulex oce driver is listed in the list of supported drivers(
http://dpdk.org/doc/nics )
Below is the detailed information:
[root@Rhel67GA-Valencia DPDK2]# ./l2fwd -c f -n 4 -- -q 8 -p ffff
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 0 on socket 1
EAL: Detected lcore 2 as core 1 on socket 0
EAL: Detected lcore 3 as core 1 on socket 1
EAL: Detected lcore 4 as core 2 on socket 0
EAL: Detected lcore 5 as core 2 on socket 1
EAL: Detected lcore 6 as core 3 on socket 0
EAL: Detected lcore 7 as core 3 on socket 1
EAL: Detected lcore 8 as core 4 on socket 0
EAL: Detected lcore 9 as core 4 on socket 1
EAL: Detected lcore 10 as core 5 on socket 0
EAL: Detected lcore 11 as core 5 on socket 1
EAL: Detected lcore 12 as core 6 on socket 0
EAL: Detected lcore 13 as core 6 on socket 1
EAL: Detected lcore 14 as core 7 on socket 0
EAL: Detected lcore 15 as core 7 on socket 1
EAL: Detected lcore 16 as core 0 on socket 0
EAL: Detected lcore 17 as core 0 on socket 1
EAL: Detected lcore 18 as core 1 on socket 0
EAL: Detected lcore 19 as core 1 on socket 1
EAL: Detected lcore 20 as core 2 on socket 0
EAL: Detected lcore 21 as core 2 on socket 1
EAL: Detected lcore 22 as core 3 on socket 0
EAL: Detected lcore 23 as core 3 on socket 1
EAL: Detected lcore 24 as core 4 on socket 0
EAL: Detected lcore 25 as core 4 on socket 1
EAL: Detected lcore 26 as core 5 on socket 0
EAL: Detected lcore 27 as core 5 on socket 1
EAL: Detected lcore 28 as core 6 on socket 0
EAL: Detected lcore 29 as core 6 on socket 1
EAL: Detected lcore 30 as core 7 on socket 0
EAL: Detected lcore 31 as core 7 on socket 1
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 32 lcore(s)
EAL: Setting up memory...
EAL: Ask a virtual area of 0x40000000 bytes
EAL: Virtual area found at 0x7ff3cb600000 (size = 0x40000000)
EAL: Ask a virtual area of 0x40000000 bytes
EAL: Virtual area found at 0x7ff38b400000 (size = 0x40000000)
EAL: Requesting 512 pages of size 2MB from socket 0
EAL: Requesting 512 pages of size 2MB from socket 1
EAL: TSC frequency is ~2399998 KHz
EAL: Master lcore 0 is ready (tid=bb39880;cpuset=[0])
PMD: ENICPMD trace: rte_enic_pmd_init
EAL: lcore 1 is ready (tid=8a5f0700;cpuset=[1])
EAL: lcore 2 is ready (tid=89bef700;cpuset=[2])
EAL: lcore 3 is ready (tid=891ee700;cpuset=[3])
EAL: Error - exiting with code: 1
Cause: No Ethernet ports – bye
Please let me know how to proceed on this.
Thanks,
Murali
--
Regards,
Vladimir
next prev parent reply other threads:[~2016-03-18 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 15:11 Murali Krishna
2016-03-18 15:21 ` Vladimir Medvedkin
2016-03-18 15:26 ` Murali Krishna
2016-03-18 15:46 ` Murali Krishna [this message]
2016-03-18 17:18 ` Vladimir Medvedkin
2016-03-18 18:08 ` Murali Krishna
2016-03-19 1:04 Krishna Mohan
2016-03-21 7:24 ` Murali Krishna
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=b8c56169bd576074835cf3baefb9df19@mail.gmail.com \
--to=murali.krishna@broadcom.com \
--cc=medvedkinv@gmail.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).