On Tue, May 9, 2017 at 1:37 PM, Shannon Nelson
<shannon.nel...@oracle.com> wrote:
> On the SPARC platform we need to use the DMA_ATTR_WEAK_ORDERING attribute
> in our Rx path dma mapping in order to get the expected performance out
> of the receive path. Adding it to the Tx path has little effect, so
> that's not a part of this patch.
>
> Signed-off-by: Shannon Nelson <shannon.nel...@oracle.com>
> Reviewed-by: Tushar Dave <tushar.n.d...@oracle.com>
> Reviewed-by: Tom Saeger <tom.sae...@oracle.com>
> ---
> drivers/net/ethernet/broadcom/bnxt/bnxt.c | 61 ++++++++++++++++++----------
> 1 files changed, 39 insertions(+), 22 deletions(-)
>
> diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> index 1f1e54b..771742c 100644
> --- a/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> +++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> @@ -66,6 +66,12 @@
> MODULE_DESCRIPTION("Broadcom BCM573xx network driver");
> MODULE_VERSION(DRV_MODULE_VERSION);
>
> +#ifdef CONFIG_SPARC
> +#define BNXT_DMA_ATTRS DMA_ATTR_WEAK_ORDERING
> +#else
> +#define BNXT_DMA_ATTRS 0
> +#endif
> +
I think we can use the same attribute for all architectures.
Architectures that don't implement weak ordering will ignore the
attribute.
