Re: [dpdk-dev] [PATCH 4/8] net/mlx4: optimize Tx multi-segment case

2017-12-06 Thread Adrien Mazarguil
On Wed, Dec 06, 2017 at 11:29:38AM +, Matan Azrad wrote: > Hi Adrien > > > -Original Message- > > From: Adrien Mazarguil [mailto:adrien.mazarg...@6wind.com] > > Sent: Wednesday, December 6, 2017 12:59 PM > > To: Matan Azrad > > Cc: dev@dpdk.org > > Subject: Re: [PATCH 4/8] net/mlx4: o

Re: [dpdk-dev] [PATCH 4/8] net/mlx4: optimize Tx multi-segment case

2017-12-06 Thread Matan Azrad
Hi Adrien > -Original Message- > From: Adrien Mazarguil [mailto:adrien.mazarg...@6wind.com] > Sent: Wednesday, December 6, 2017 12:59 PM > To: Matan Azrad > Cc: dev@dpdk.org > Subject: Re: [PATCH 4/8] net/mlx4: optimize Tx multi-segment case > > On Tue, Nov 28, 2017 at 12:19:26PM +,

Re: [dpdk-dev] [PATCH 4/8] net/mlx4: optimize Tx multi-segment case

2017-12-06 Thread Adrien Mazarguil
On Tue, Nov 28, 2017 at 12:19:26PM +, Matan Azrad wrote: > mlx4 Tx block can handle up to 4 data segments or control segment + up > to 3 data segments. The first data segment in each not first Tx block > must validate Tx queue wraparound and must use IO memory barrier before > writing the byte

[dpdk-dev] [PATCH 4/8] net/mlx4: optimize Tx multi-segment case

2017-11-28 Thread Matan Azrad
mlx4 Tx block can handle up to 4 data segments or control segment + up to 3 data segments. The first data segment in each not first Tx block must validate Tx queue wraparound and must use IO memory barrier before writing the byte count. The previous multi-segment code used "for" loop to iterate ov