[ovs-dev] [PATCH v6 0/1] Balance-tcp bond mode optimization

Vishal Deep Ajmera vishal.deep.ajmera at ericsson.com
Sat Sep 14 13:32:54 UTC 2019


> >
> > I confirm a decent performance improvement with DPDK and balance-tcp
> bonding:
> >
> > lb-output-action=false
> >
> > rx: 740 Mbps 1446 kpps
> >
> > lb-output-action=true
> >
> > rx: 860 Mbps 1680 kpps
> >
> > I'm running a very simple test with a tweaked version of testpmd which
> > generates 256 L4 flows, I guess that with much flows the improvement
> > is way higher.
> >
> > Tested-by: Matteo Croce <mcroce at redhat.com>
> >

Thank you Matteo for testing this patch.

> I found an issue with the patch. It's not 100% reproducible, but sometimes 
> the
> option gets enabled regardless of the bonding type and the configuration.
> This breaks the unit tests, as the bond/show output is wrong:
>
> # ovs-vsctl add-br br0
> [63129.589500] device ovs-system entered promiscuous mode [63129.591802]
> device br0 entered promiscuous mode
>
> # ovs-vsctl add-bond br0 bond dummy0 dummy1 -- set Port bond lacp=active
> bond-mode=active-backup [63150.700542] device dummy1 entered
> promiscuous mode [63150.700892] device dummy0 entered promiscuous mode
>
Let me check this in my setup. I always used 'netdev' bridges for testing my 
patch.
May be I need to be check for data path support in the display function as 
well.


More information about the dev mailing list