[ovs-dev] [ovs-dev, ovs-dev, v4] netdev-dpdk: Configurable Link State Change (LSC) detection mode

Róbert Mulik robert.mulik at ericsson.com
Mon Feb 5 14:34:53 UTC 2018


It was triggered right after the change. This was my ovs setup:

ovs-vsctl show
57390393-2b8b-4aba-b5dc-aaf822138e66
    Bridge br-prv
        Port "dpdk0"
            Interface "dpdk0"
                type: dpdk
                options: {dpdk-devargs="0000:83:00.1", n_rxq="2"}
        Port br-prv
            Interface br-prv
                type: internal
        Port "dpdk1"
            Interface "dpdk1"
                type: dpdk
                options: {dpdk-devargs="0000:01:00.0", n_rxq="2"}
    ovs_version: "2.9.90"


-----Original Message-----
From: Ilya Maximets [mailto:i.maximets at samsung.com] 
Sent: Monday, February 05, 2018 3:31 PM
To: Róbert Mulik <robert.mulik at ericsson.com>; dev at openvswitch.org
Cc: Stokes, Ian <ian.stokes at intel.com>; Eelco Chaudron <echaudro at redhat.com>
Subject: Re: [ovs-dev, ovs-dev, v4] netdev-dpdk: Configurable Link State Change (LSC) detection mode

On 05.02.2018 17:18, Róbert Mulik wrote:
> Hi Ilya,
> 
> As I see you are concerned if the code is working, also Eelco mentioned that the configuration change didn't take effect for him, so I retested the patch.
> 
> I added 2 different types of NICs to OVS on the same server:
> 
> 1
> product: 82599ES 10-Gigabit SFI/SFP+ Network Connection It uses ixgbe 
> kernel driver by default
> 
> 2
> product: Ethernet Controller XL710 for 40GbE QSFP+ It uses i40e kernel 
> driver by default
> 
> In my setup I used a Dell 630 with kernel 4.4.0-111-generic, and used vfio-pci kernel driver for the NICs.
> 
> I monitored the link_state of the dpdk interfaces and the interrupt counters of /proc/interrupts.
> 
> When I changed either the other_config:dpdk-lsc-interrupt part of 
> Open_vSwitch, or the options:dpdk-lsc-interrupt part of the NIC by set 
> or remove, the behavior was correct: the link_state always changed 
> when reinitialization was triggered,


That is the key point. When the reinitialization was actually triggered?
Was it triggered right after changing the other_config:dpdk-lsc-interrupt ?
Or you need some additional manipulations to trigger the actual reconfiguration?

> however there were problems with the counters.
> 
> 1.
> This NIC worked fine, link_state was OK, interrupt counters were incremented as expected.
> 
> 2.
> The link_state was OK, but there were problems with the counters.
> 
> With the X710 series there are a few problems related to the 
> link_state and interrupts known by intel too. The faulty behavior can be caused by the combination of the FW of the NIC, the kernel version, the dpdk version, and the i40e kernel driver version (there can be interference between the kernel driver and dpdk driver).
> 
> 
> After the verification, as I see the code works fine (the events triggered when the options are changed), but the XL710 card has problems with the interrupt configuration.
> 
> Eelco, I know that you are working with X710 series cards. Did you test the patch on one of them, or on a different type?
> When (if) you verify the patch, could you please check it on different NICs too?
> 
> Thank you!
> 
> Regards,
> Robert
> 


More information about the dev mailing list