Re: [lng-odp] problem about odp-ovs(with dpdk)

2018-01-16 Thread lin huang
Thank you!!!

I did the commands:
/home/vagrant/dpdk/usertools/dpdk-devbind.py --bind=igb_uio :00:08.0
/home/vagrant/dpdk/usertools/dpdk-devbind.py --bind=igb_uio :00:09.0

And the dvebind tool status shows:

root@vagrant:/home/vagrant/dpdk# ./usertools/dpdk-devbind.py --status
Network devices using DPDK-compatible driver

:00:08.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=e1000
:00:09.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=e1000

Network devices using kernel driver
===
:00:03.0 '82540EM Gigabit Ethernet Controller' if=enp0s3 drv=e1000 
unused=igb_uio *Active*

But I still can't add port to odp-ovs. 
odp-ovs project only support to odp-linux ?

>>-Original Message-
>>From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of Bogdan
>>Pricope
>>Sent: Tuesday, January 16, 2018 9:07 PM
>>To: Maxim Uvarov <maxim.uva...@linaro.org>
>>Cc: lng-odp-forward <lng-odp@lists.linaro.org>
>>Subject: Re: [lng-odp] problem about odp-ovs(with dpdk)
>>
>>See below commands (adapt to your PCI IDs and driver):
>>
>>${DPDK_PATH}/usertools/dpdk-devbind.py -s
>>${DPDK_PATH}/usertools/dpdk-devbind.py -u :01:00.0
>>${DPDK_PATH}usertools/dpdk-devbind.py -u :01:00.1
>>${DPDK_PATH}/usertools/dpdk-devbind.py --bind=igb_uio  :01:00.0
>>${DPDK_PATH}/usertools/dpdk-devbind.py --bind=igb_uio  :01:00.1
>>
>>On 16 January 2018 at 14:36, Maxim Uvarov <maxim.uva...@linaro.org>
>>wrote:
>>> On 01/16/18 10:35, lin huang wrote:
>>>> Hi guys,
>>>>I get a problem when I try to use odp-ovs with odp-dpdk.
>>>> I compiled the odp-dpdk and odp-ovs successfully. and then I want to try 
>>>> add
>>a port to ovs bridge with the following command:
>>>>
>>>> ovs-vsctl add-port br0 odp:enp0s8 -- set Interface odp:enp0s8
>>>> type=odp
>>>>
>>>> these commands work properly when I use odp-ovs with odp-linux.
>>>> But when I input these command when I use odp-ovs with odp-dpdk it failed.
>>>>
>>>> The ovs-vswitchd.log content:
>>>> root@vagrant:/usr/local/bin# tail
>>>> /usr/local/var/log/openvswitch/ovs-vswitchd.log
>>>> 2018-01-16T07:09:51.384Z|00049|bridge|WARN|could not open network
>>>> device odp:enp0s8 (Address family not supported by protocol)
>>2018-01-16T07:10:04.683Z|00050|odp|ERR|../linux-generic/odp_packet_io.c:
>>226:setup_pktio_entry():Unable to init any I/O type.
>>>> 2018-01-16T07:10:04.683Z|00051|odp|ERR|Error: odp_pktio_open() failed
>>>> 2018-01-16T07:10:04.685Z|00052|bridge|WARN|could not open network
>>>> device odp:enp0s8 (No such file or directory)
>>>>
>>>> So, are there somebody knows how it work?? Or how to configure it???
>>>> I need you help
>>>>
>>>> Thank you very much!!
>>>>
>>>
>>> In dpdk interfaces names are numbers 0, 1, 2. And you need
>>> dpdk-devbind.py to move nic from linux mode to kernel mode.
>>> You can find example how to do it from this log:
>>> https://lng.validation.linaro.org/scheduler/job/23296.1
>>>
>>> Best regards,
>>> Maxim.


Re: [lng-odp] problem about odp-ovs(with dpdk)

2018-01-16 Thread Bogdan Pricope
See below commands (adapt to your PCI IDs and driver):

${DPDK_PATH}/usertools/dpdk-devbind.py -s
${DPDK_PATH}/usertools/dpdk-devbind.py -u :01:00.0
${DPDK_PATH}usertools/dpdk-devbind.py -u :01:00.1
${DPDK_PATH}/usertools/dpdk-devbind.py --bind=igb_uio  :01:00.0
${DPDK_PATH}/usertools/dpdk-devbind.py --bind=igb_uio  :01:00.1

On 16 January 2018 at 14:36, Maxim Uvarov  wrote:
> On 01/16/18 10:35, lin huang wrote:
>> Hi guys,
>>I get a problem when I try to use odp-ovs with odp-dpdk.
>> I compiled the odp-dpdk and odp-ovs successfully. and then I want to try add 
>> a port to ovs bridge with the following command:
>>
>> ovs-vsctl add-port br0 odp:enp0s8 -- set Interface odp:enp0s8 type=odp
>>
>> these commands work properly when I use odp-ovs with odp-linux.
>> But when I input these command when I use odp-ovs with odp-dpdk it failed.
>>
>> The ovs-vswitchd.log content:
>> root@vagrant:/usr/local/bin# tail 
>> /usr/local/var/log/openvswitch/ovs-vswitchd.log
>> 2018-01-16T07:09:51.384Z|00049|bridge|WARN|could not open network device 
>> odp:enp0s8 (Address family not supported by protocol)
>> 2018-01-16T07:10:04.683Z|00050|odp|ERR|../linux-generic/odp_packet_io.c:226:setup_pktio_entry():Unable
>>  to init any I/O type.
>> 2018-01-16T07:10:04.683Z|00051|odp|ERR|Error: odp_pktio_open() failed
>> 2018-01-16T07:10:04.685Z|00052|bridge|WARN|could not open network device 
>> odp:enp0s8 (No such file or directory)
>>
>> So, are there somebody knows how it work?? Or how to configure it???
>> I need you help
>>
>> Thank you very much!!
>>
>
> In dpdk interfaces names are numbers 0, 1, 2. And you need
> dpdk-devbind.py to move nic from linux mode to kernel mode.
> You can find example how to do it from this log:
> https://lng.validation.linaro.org/scheduler/job/23296.1
>
> Best regards,
> Maxim.


Re: [lng-odp] problem about odp-ovs(with dpdk)

2018-01-16 Thread Maxim Uvarov
On 01/16/18 10:35, lin huang wrote:
> Hi guys,
>I get a problem when I try to use odp-ovs with odp-dpdk.
> I compiled the odp-dpdk and odp-ovs successfully. and then I want to try add 
> a port to ovs bridge with the following command:
> 
> ovs-vsctl add-port br0 odp:enp0s8 -- set Interface odp:enp0s8 type=odp
> 
> these commands work properly when I use odp-ovs with odp-linux.
> But when I input these command when I use odp-ovs with odp-dpdk it failed.
> 
> The ovs-vswitchd.log content:
> root@vagrant:/usr/local/bin# tail 
> /usr/local/var/log/openvswitch/ovs-vswitchd.log
> 2018-01-16T07:09:51.384Z|00049|bridge|WARN|could not open network device 
> odp:enp0s8 (Address family not supported by protocol)
> 2018-01-16T07:10:04.683Z|00050|odp|ERR|../linux-generic/odp_packet_io.c:226:setup_pktio_entry():Unable
>  to init any I/O type.
> 2018-01-16T07:10:04.683Z|00051|odp|ERR|Error: odp_pktio_open() failed
> 2018-01-16T07:10:04.685Z|00052|bridge|WARN|could not open network device 
> odp:enp0s8 (No such file or directory)
> 
> So, are there somebody knows how it work?? Or how to configure it???
> I need you help
> 
> Thank you very much!!
> 

In dpdk interfaces names are numbers 0, 1, 2. And you need
dpdk-devbind.py to move nic from linux mode to kernel mode.
You can find example how to do it from this log:
https://lng.validation.linaro.org/scheduler/job/23296.1

Best regards,
Maxim.