[dpdk-dev] Issue with l2fwd in kvm guest

2014-04-11 Thread Ajith Adapa
Hi,

I am just trying out DPDK in a fedora 18 KVM guest and have an issue when I
am trying l2fwd application.

I am binding eth1, eth2 interfaces using below commands

./igb_uio_bind.py --bind=igb_uio eth1
./igb_uio_bind.py --bind=igb_uio eth2

When I run l2fwd app I get following error

./l2fwd -c 1 -n 4
EAL: Cannot read numa node link for lcore 0 - using physical package id
instead
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Setting up memory...
EAL: cannot open /proc/self/numa_maps, consider that all memory is in
socket_id 0
EAL: Ask a virtual area of 0x1880 bytes
EAL: Virtual area found at 0x9dc0 (size = 0x1880)
EAL: Ask a virtual area of 0x40 bytes
EAL: Virtual area found at 0x9d40 (size = 0x40)
EAL: Ask a virtual area of 0x40 bytes
EAL: Virtual area found at 0x9cc0 (size = 0x40)
EAL: Requesting 100 pages of size 4MB from socket 0
EAL: TSC frequency is ~3191735 KHz
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable
clock cycles !
EAL: Master core 0 is ready (tid=b7782800)
EAL: PCI device :00:03.0 on NUMA socket -1
EAL:   probe driver: 1af4:1000 rte_virtio_pmd
EAL:   :00:03.0 not managed by UIO driver, skipping
EAL: PCI device :00:07.0 on NUMA socket -1
EAL:   probe driver: 8086:100e rte_em_pmd
EAL:   PCI memory mapped at 0xb7732000
EAL: PCI device :00:08.0 on NUMA socket -1
EAL:   probe driver: 8086:100e rte_em_pmd
EAL:   PCI memory mapped at 0xb7712000
Skipping disabled port 0
Skipping disabled port 1
EAL: Error - exiting with code: 1
  Cause: All available ports are disabled. Please set portmask.

Dmesg logs after binding eth1 and eth2 to igb_uio

[5.700591] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: RX
[5.733457] e1000: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow
Control: RX
[   55.835017] igb_uio: module verification failed: signature and/or
required key missing - tainting kernel
[   55.835888] Use MSIX interrupt by default
[   56.035098] igb_uio :00:07.0: setting latency timer to 64
[   56.035123] fail to enable pci msix, or not enough msix entries
[   56.035492] uio device registered with irq a
[   56.184789] igb_uio :00:08.0: setting latency timer to 64
[   56.184811] fail to enable pci msix, or not enough msix entries
[   56.184969] uio device registered with irq b
[  589.675041] Bits 55-60 of /proc/PID/pagemap entries are about to stop
being page-shift some time soon. See the linux/Documentation/vm/pagemap.txt
for details.

Can anyone point me to right direction regarding where I am doing the
mistake ?

Regards,
Ajith


[dpdk-dev] vETH is DOWN by default

2014-06-05 Thread Ajith Adapa
Hi,

We are running the sample DPDK KNI application on a single physical port.
We are able to see the vETH interface getting created via IFCONFIG.
However the vETH interface is DOWN by default despite the physical
interface being UP and RUNNING. Only when we configured IP address via
IFCONFIG, the vETH came UP. Any reason for this ?

Regards,
Ajith