[dpdk-dev] KNI interface operational state UP issue

DPDK patches and discussions
 help / color / mirror / Atom feed

From: Aziz Hajee <aziz@saisei.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] KNI interface operational state UP issue
Date: Fri, 9 Jan 2015 17:20:26 -0800	[thread overview]
Message-ID: <CAFGSfknTNGabm_+2o7TTQE-HN-exXkGFzuNj83hDTDvwUSRwZw@mail.gmail.com> (raw)

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.


Thanks,
-aziz
===========================================
dmesg shows the KNI module driver and creating the KNI interfaces:

[ 1349.192958] KNI: ######## DPDK kni module loading ########
[ 1349.193003] KNI: loopback disabled
[ 1349.193004] KNI: ######## DPDK kni module loaded  ########
.....

[ 1503.695034] KNI: Single kernel thread for all KNI devices
[ 1503.695109] KNI: /dev/kni opened
[ 1503.695122] KNI: IOCTL num=0xc0880002 param=0x7f76c77fcb10
[ 1503.695123] KNI: Creating kni...
[ 1503.695128] KNI: kni_net_init
......
...
[ 1503.695139] KNI: PCI: 06:00.00 8086:10fb
[ 1503.695142] KNI: pci_bus: 06:00:00
[ 1503.734041] igb_uio 0000:06:00.0: (PCI Express:5.0GT/s:Width x8)
[ 1503.734046] 90:e2:ba:5f:1a:64
[ 1503.734138] igb_uio 0000:06:00.0 (unregistered net_device): MAC: 2, PHY:
0, PBA No: E68793-006
[ 1503.734197] igb_uio 0000:06:00.0 (unregistered net_device): Enabled
Features: RxQ: 1 TxQ: 1
[ 1503.734226] igb_uio 0000:06:00.0 (unregistered net_device): Intel(R) 10
Gigabit Network Connection
[ 1503.734228] KNI: PCI found: pci=0xffff882ff99db000,
lad_dev=0xffff882ff33c0000
[ 1503.734674] KNI: IOCTL num=0xc0880002 param=0x7f76c77fcb10
[ 1503.734675] KNI: Creating kni...
[ 1503.734680] KNI: kni_net_init
.......
[ 1503.734690] KNI: PCI: 06:00.01 8086:10fb
[ 1503.734693] KNI: pci_bus: 06:00:00
[ 1503.734694] KNI: pci_bus: 06:00:01
[ 1503.774033] igb_uio 0000:06:00.1: (PCI Express:5.0GT/s:Width x8)
[ 1503.774038] 90:e2:ba:5f:1a:65
[ 1503.774129] igb_uio 0000:06:00.1 (unregistered net_device): MAC: 2, PHY:
0, PBA No: E68793-006
[ 1503.774154] igb_uio 0000:06:00.1 (unregistered net_device): Enabled
Features: RxQ: 1 TxQ: 1
[ 1503.774169] igb_uio 0000:06:00.1 (unregistered net_device): Intel(R) 10
Gigabit Network Connection
[ 1503.774184] KNI: PCI found: pci=0xffff882ff99dc000,
lad_dev=0xffff882ff3870000

next             reply	other threads:[~2015-01-10  1:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-10  1:20 Aziz Hajee [this message]
2015-01-12 11:24 ` Bruce Richardson
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=CAFGSfknTNGabm_+2o7TTQE-HN-exXkGFzuNj83hDTDvwUSRwZw@mail.gmail.com \
    --to=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).