From: Bruce Richardson <bruce.richardson@intel.com>
To: Aziz Hajee <aziz@saisei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] KNI interface operational state UP issue
Date: Mon, 12 Jan 2015 11:24:43 +0000 [thread overview]
Message-ID: <20150112112443.GB13136@bricha3-MOBL3> (raw)
In-Reply-To: <CAFGSfknTNGabm_+2o7TTQE-HN-exXkGFzuNj83hDTDvwUSRwZw@mail.gmail.com>
On Fri, Jan 09, 2015 at 05:20:26PM -0800, Aziz Hajee wrote:
> I am using the dpdk1.6.0r1
> The rte_kni.lo is loaded:
> lsmod | grep kni
> rte_kni 279134 1
>
> however, the ifconfig vEth0, and vEth1 does not show link up ?
> How do i get the operational state up for these interfaces.
> $ sudo tcpdump -i vEth0
> tcpdump: vEth0: That device is not up
>
> ifconfig vEth0
> vEth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:12 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:3388 (3.3 KB) TX bytes:0 (0.0 B)
>
> ifconfig vEth1
> vEth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:60 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:10252 (10.2 KB) TX bytes:0 (0.0 B)
>
> These KNI interfaces are created as per dmeg below from the CREATE IOCTL.
> sudo ifconfig vEth0 192.168.0.11 netmask 255.255.0.0
> SIOCSIFFLAGS: Timer expired
> aziz@fast-1:~/stm15-0108/stm/dpdk/dpdk-1.6.0r1_ss/lib/librte_eal/linuxapp/kni$
> ifconfig vEth0
> vEth0 Link encap:Ethernet HWaddr 90:e2:ba:5f:1a:64
> inet addr:192.168.0.11 Bcast:192.168.255.255 Mask:255.255.0.0
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:50 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:14488 (14.4 KB) TX bytes:0 (0.0 B)
>
> Trying to set the vEth0 up, looks like it is doing the callback in the dpdk
> to the corresponding PMD NIC interface, and not the vEth0 kernel interface.
>
With KNI, the actual underlying NIC interface is still under the control of the
DPDK application. What happens is that any ethtool requests that go to the kernel
driver, get passed into the userspace DPDK application to make the actual changes
to the hardware port. Does DPDK itself report the port as being up?
/Bruce
next prev parent reply other threads:[~2015-01-12 11:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 1:20 Aziz Hajee
2015-01-12 11:24 ` Bruce Richardson [this message]
2015-01-15 0:59 ` Aziz Hajee
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=20150112112443.GB13136@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=aziz@saisei.com \
--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).