From: BYEONG-GI KIM <kimbyeonggi@gmail.com>
To: dev@dpdk.org, Dpdk-ovs@lists.01.org
Subject: [dpdk-dev] a NIC binding to igb_uio module of DPDK is down
Date: Wed, 13 Aug 2014 13:27:12 +0900 [thread overview]
Message-ID: <CAEHt_JbS3FSYQoJ24KxJi-NE6aQfw5Q5XFYd4oGMU6NjrRiBiw@mail.gmail.com> (raw)
Hello.
I deployed openstack with dpdk-ovs and I'm now testing it.
The problem is that a NIC which is binding to igb_uio module of DPDK is
physically down so that it seems not communicate with the other hosts
through the NIC.
The test environment is as below:
OS: RHEL 6 with kernel 3.7.10
Hardware information: Intel Atom Processor C2758, 64GB DDR3, 4x RJ45
Gigabit Ethernet LAN ports, etc.
DPDK version: 1.7.0
ovdk version: 1.1
I checked the NIC's status via ./tools/dpdk_nic_bind.py --status, and it
doesn't snow *Active* status:
./tools/dpdk_nic_bind.py --status
Network devices using DPDK-compatible driver
============================================
0000:00:14.1 'Ethernet Connection I354' drv=igb_uio unused=igb
Network devices using kernel driver
===================================
0000:00:14.0 'Ethernet Connection I354' if=eth0 drv=igb unused=igb_uio
*Active*
0000:00:14.2 'Ethernet Connection I354' if=eth2 drv=igb unused=igb_uio
*Active*
0000:00:14.3 'Ethernet Connection I354' if=eth3 drv=igb unused=igb_uio
Other network devices
=====================
<none>
The NIC port on the PC doesn't glitter physically, which means it seems not
connected physically.
Doesn't the processor support DPDK, or what is causing the problem?
Any comments would be really appreciated.
Best Regards
Byeong-Gi KIM
next reply other threads:[~2014-08-13 4:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 4:27 BYEONG-GI KIM [this message]
2014-08-13 6:30 ` Wodkowski, PawelX
2014-08-13 16:25 ` Richardson, Bruce
2014-08-13 7:11 ` Choi, Sy Jong
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=CAEHt_JbS3FSYQoJ24KxJi-NE6aQfw5Q5XFYd4oGMU6NjrRiBiw@mail.gmail.com \
--to=kimbyeonggi@gmail.com \
--cc=Dpdk-ovs@lists.01.org \
--cc=dev@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).