patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: stable@dpdk.org, nd@arm.com,
	 Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Subject: Re: [PATCH 19.11] net/i40e: fix risk in descriptor read in NEON Rx
Date: Wed, 1 Dec 2021 11:31:24 +0100	[thread overview]
Message-ID: <CAATJJ0Lfxhaej0HnQsFst4J7OncxerpWA7ogvn_P82i55G91+A@mail.gmail.com> (raw)
In-Reply-To: <20211201074811.1590896-1-ruifeng.wang@arm.com>

On Wed, Dec 1, 2021 at 8:48 AM Ruifeng Wang <ruifeng.wang@arm.com> wrote:
>
> [ upstream commit 778602fe570a138224de94a38eca3ce2e344138c ]
>

Thanks, applied

> Rx descriptor is 16B/32B in size. If the DD bit is set, it indicates
> that the rest of the descriptor words have valid values. Hence, the
> word containing DD bit must be read first before reading the rest of
> the descriptor words.
>
> In NEON vector PMD, vector load loads two contiguous 8B of
> descriptor data into vector register. Given vector load ensures no
> 16B atomicity, read of the word that includes DD field could be
> reordered after read of other words. In this case, some words could
> contain invalid data.
>
> Read barrier is added after read of qword1 that includes DD field.
> And qword0 is reloaded to update vector register. This ensures
> that the fetched data is correct.
>
> Testpmd single core test on N1SDP/ThunderX2 showed no performance drop.
>
> Fixes: ae0eb310f253 ("net/i40e: implement vector PMD for ARM")
>
> Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> ---
>  drivers/net/i40e/i40e_rxtx_vec_neon.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
>
> diff --git a/drivers/net/i40e/i40e_rxtx_vec_neon.c b/drivers/net/i40e/i40e_rxtx_vec_neon.c
> index bd1e0490d..0da6b37da 100644
> --- a/drivers/net/i40e/i40e_rxtx_vec_neon.c
> +++ b/drivers/net/i40e/i40e_rxtx_vec_neon.c
> @@ -299,6 +299,14 @@ _recv_raw_pkts_vec(struct i40e_rx_queue *rxq, struct rte_mbuf **rx_pkts,
>                 /* B.2 copy 2 mbuf point into rx_pkts  */
>                 vst1q_u64((uint64_t *)&rx_pkts[pos + 2], mbp2);
>
> +               /* Use acquire fence to order loads of descriptor qwords */
> +               __atomic_thread_fence(__ATOMIC_ACQUIRE);
> +               /* A.2 reload qword0 to make it ordered after qword1 load */
> +               descs[3] = vld1q_lane_u64((uint64_t *)(rxdp + 3), descs[3], 0);
> +               descs[2] = vld1q_lane_u64((uint64_t *)(rxdp + 2), descs[2], 0);
> +               descs[1] = vld1q_lane_u64((uint64_t *)(rxdp + 1), descs[1], 0);
> +               descs[0] = vld1q_lane_u64((uint64_t *)(rxdp), descs[0], 0);
> +
>                 if (split_packet) {
>                         rte_mbuf_prefetch_part2(rx_pkts[pos]);
>                         rte_mbuf_prefetch_part2(rx_pkts[pos + 1]);
> --
> 2.25.1
>


-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

      reply	other threads:[~2021-12-01 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-01  7:48 Ruifeng Wang
2021-12-01 10:31 ` Christian Ehrhardt [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=CAATJJ0Lfxhaej0HnQsFst4J7OncxerpWA7ogvn_P82i55G91+A@mail.gmail.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=nd@arm.com \
    --cc=ruifeng.wang@arm.com \
    --cc=stable@dpdk.org \
    /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).