Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1384537

Re: [PATCH] ixgbevf: Fix relaxed order settings in VF driver

From Babu Moger <babu.moger@oracle.com>
Newsgroups linux.kernel
Subject Re: [PATCH] ixgbevf: Fix relaxed order settings in VF driver
Date 2016-04-21 21:50 +0200
Message-ID <rqsLV-6db-27@gated-at.bofh.it> (permalink)
References <rqqAq-4fG-1@gated-at.bofh.it> <rqrmO-52G-19@gated-at.bofh.it> <rqssy-642-3@gated-at.bofh.it>
Organization Oracle Corporation

Show all headers | View raw


Hi Alex,

On 4/21/2016 2:22 PM, Alexander Duyck wrote:
> On Thu, Apr 21, 2016 at 11:13 AM, Alexander Duyck
> <alexander.duyck@gmail.com> wrote:
>> On Thu, Apr 21, 2016 at 10:21 AM, Babu Moger <babu.moger@oracle.com> wrote:
>>> Current code writes the tx/rx relaxed order without reading it first.
>>> This can lead to unintended consequences as we are forcibly writing
>>> other bits.
>>
>> The consequences were very much intended as there are situations where
>> enabling relaxed ordering can lead to data corruption.
>>
>>> We noticed this problem while testing VF driver on sparc. Relaxed
>>> order settings for rx queue were all messed up which was causing
>>> performance drop with VF interface.
>>
>> What additional relaxed ordering bits are you enabling on Sparc?  I'm
>> assuming it is just the Rx data write back but I want to verify.
>>
>>> Fixed it by reading the registers first and setting the specific
>>> bit of interest. With this change we are able to match the bandwidth
>>> equivalent to PF interface.
>>>
>>> Signed-off-by: Babu Moger <babu.moger@oracle.com>
>>
>> Fixed is a relative term here since you are only chasing performance
>> from what I can tell.  We need to make certain that this doesn't break
>> the driver on any other architectures by leading to things like data
>> corruption.
>>
>> - Alex
> 
> It occurs to me that what might be easier is instead of altering the
> configuration on all architectures you could instead wrap the write so
> that on SPARC you include the extra bits you need and on all other
> architectures you leave the write as-is similar to how the code in the
> ixgbe_start_hw_gen2 only clears the bits if CONFIG_SPARC is not
> defined.


Here are the default values that I see when testing on Sparc.

Default tx value 0x2a00

All below 3 set
#define IXGBE_DCA_TXCTRL_DESC_RRO_EN (1 << 9) /* Tx rd Desc Relax Order */
#define IXGBE_DCA_TXCTRL_DESC_WRO_EN (1 << 11) /* Tx Desc writeback RO bit */
#define IXGBE_DCA_TXCTRL_DATA_RRO_EN (1 << 13) /* Tx rd data Relax Order */

I am not too worried about tx values. I can keep it as it is. It did not
seem to cause any problems right now.


Default rx value 0xb200

All below 3 set plus one more

#define IXGBE_DCA_RXCTRL_DESC_RRO_EN (1 << 9) /* DCA Rx rd Desc Relax Order */
#define IXGBE_DCA_RXCTRL_DATA_WRO_EN (1 << 13) /* Rx wr data Relax Order */
#define IXGBE_DCA_RXCTRL_HEAD_WRO_EN (1 << 15) /* Rx wr header RO */

Is there a reason to disable IXGBE_DCA_RXCTRL_DATA_WRO_EN and
IXGBE_DCA_RXCTRL_HEAD_WRO_EN for RX? 

I would think CONFIG_SPARC should be our last option. What do you think?

> 
> - Alex
> 

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH] ixgbevf: Fix relaxed order settings in VF driver Babu Moger <babu.moger@oracle.com> - 2016-04-21 19:30 +0200
  Re: [PATCH] ixgbevf: Fix relaxed order settings in VF driver Alexander Duyck <alexander.duyck@gmail.com> - 2016-04-21 20:20 +0200
    Re: [PATCH] ixgbevf: Fix relaxed order settings in VF driver Alexander Duyck <alexander.duyck@gmail.com> - 2016-04-21 21:30 +0200
      Re: [PATCH] ixgbevf: Fix relaxed order settings in VF driver Babu Moger <babu.moger@oracle.com> - 2016-04-21 21:50 +0200
        Re: [PATCH] ixgbevf: Fix relaxed order settings in VF driver Alexander Duyck <alexander.duyck@gmail.com> - 2016-04-21 23:10 +0200

csiph-web