Re: [dpdk-dev] [dpdk-ovs] Problem with OVS

[Romulo Rosa <romuloros@gmail.com>]

Thanks Paul,

But i think my NICS are not supportted by Intel DPDK. In this link they are
not listed http://dpdk.org/doc/nics. Anyone know if there are other
supported cards?

./tools/pci_unbind.py --status

Network devices using IGB_UIO driver
====================================
<none>

Network devices using kernel driver
===================================
0000:03:00.0 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eth0
*drv=tg3* unused=
*Active*
0000:03:00.1 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eth1 *drv=tg3*
 unused=
0000:03:00.2 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eth2 *drv=tg3*
 unused=
0000:03:00.3 'NetXtreme BCM5719 Gigabit Ethernet PCIe' if=eth3 *drv=tg3*
 unused=
0000:07:00.0 'OneConnect 10Gb NIC (be3)' if=eth4* drv=be2net* unused=
0000:07:00.1 'OneConnect 10Gb NIC (be3)' if=eth5 *drv=be2net* unused=

Other network devices
=====================
<none>


2013/12/13 Paul Barrette <paul.barrette@windriver.com>

>
> On 12/12/2013 05:25 PM, Romulo Rosa wrote:
>
>> Hi,
>>
>> i'm tryin to run OVS and i get a error. In documentation was mentioned a
>> possible solution for this problem but it didnt work to me. Someone have
>> any idea how to solve this problem?
>> The uio module is loaded.
>>
>> *Command: *./datapath/dpdk/build/ovs_dpdk -c 0xf -n 4 -- -p 0xc
>>
> I think you have the wrong port mask.  Try using -p 0x3.
>
> Pb
>
>>   -n 2 -k 2
>> --stats=1 --vswitchd=0 --client_switching_core=1
>> --config="(0,0,2),(1,0,3)"
>>
>> *Error: *
>>
>> EAL: Core 2 is ready (tid=43fd700)
>> EAL: Core 3 is ready (tid=3bfc700)
>> EAL: Core 1 is ready (tid=4bfe700)
>> WARNING: requested port 2 not present - ignoring
>> WARNING: requested port 3 not present - ignoring
>> config = 16,0,2
>> config = 17,0,3
>> nb_cfg_params = 2
>> Creating mbuf pool 'MProc_pktmbuf_pool' [14336 mbufs] ...
>> HASH: Enabling CRC32 instruction for hashing
>> APP: memzone address is 2ef33980
>> EAL: Error - exiting with code: 1
>>    Cause: Cannot allocate memory for port tx_q details
>>
>> Thanks!
>>
>
>


-- 
Rômulo Rosa Furtado