DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@mellanox.com>,
	Alexander Kozyrev <akozyrev@mellanox.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix metadata storing for NEON vectorized Rx burst
Date: Thu, 23 Jul 2020 13:34:12 +0000	[thread overview]
Message-ID: <AM0PR05MB670715797DB888EBB98C28A7C2760@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1595501612-21309-1-git-send-email-viacheslavo@mellanox.com>

Hi,

> -----Original Message-----
> From: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> Sent: Thursday, July 23, 2020 1:54 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@mellanox.com>; Raslan Darawsheh
> <rasland@mellanox.com>; Alexander Kozyrev <akozyrev@mellanox.com>;
> stable@dpdk.org
> Subject: [PATCH] net/mlx5: fix metadata storing for NEON vectorized Rx
> burst
> 
> There was the typo introducing the bug, affected the mlx5 vectorized
> rx_burst on ARM architectures in case if CQE compression was enabled.
> 
> Fixes: 6c55b622a956 ("net/mlx5: set dynamic flow metadata in Rx queues")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
>  drivers/net/mlx5/mlx5_rxtx_vec_neon.h | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/net/mlx5/mlx5_rxtx_vec_neon.h
> b/drivers/net/mlx5/mlx5_rxtx_vec_neon.h
> index 6c31495..af924b7 100644
> --- a/drivers/net/mlx5/mlx5_rxtx_vec_neon.h
> +++ b/drivers/net/mlx5/mlx5_rxtx_vec_neon.h
> @@ -736,20 +736,20 @@
>  						      pkt_info)->timestamp);
>  			}
>  		}
> -		if (!!rxq->flow_meta_mask) {
> +		if (rxq->dynf_meta) {
>  			/* This code is subject for futher optimization. */
>  			int32_t offs = rxq->flow_meta_offset;
> 
>  			*RTE_MBUF_DYNFIELD(pkts[pos], offs, uint32_t *) =
>  				container_of(p0, struct mlx5_cqe,
>  					     pkt_info)->flow_table_metadata;
> -			*RTE_MBUF_DYNFIELD(pkts[pos], offs, uint32_t *) =
> +			*RTE_MBUF_DYNFIELD(pkts[pos + 1], offs, uint32_t
> *) =
>  				container_of(p1, struct mlx5_cqe,
>  					     pkt_info)->flow_table_metadata;
> -			*RTE_MBUF_DYNFIELD(pkts[pos], offs, uint32_t *) =
> +			*RTE_MBUF_DYNFIELD(pkts[pos + 2], offs, uint32_t
> *) =
>  				container_of(p2, struct mlx5_cqe,
>  					     pkt_info)->flow_table_metadata;
> -			*RTE_MBUF_DYNFIELD(pkts[pos], offs, uint32_t *) =
> +			*RTE_MBUF_DYNFIELD(pkts[pos + 3], offs, uint32_t
> *) =
>  				container_of(p3, struct mlx5_cqe,
>  					     pkt_info)->flow_table_metadata;
>  			if (*RTE_MBUF_DYNFIELD(pkts[pos], offs, uint32_t
> *))
> --
> 1.8.3.1


Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2020-07-23 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 10:53 Viacheslav Ovsiienko
2020-07-23 13:34 ` Raslan Darawsheh [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AM0PR05MB670715797DB888EBB98C28A7C2760@AM0PR05MB6707.eurprd05.prod.outlook.com \
    --to=rasland@mellanox.com \
    --cc=akozyrev@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@mellanox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).