DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Stokes, Ian" <ian.stokes@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>
Subject: RE: [PATCH 0/4] fix issues with using AVX-512 drivers on 32-bit
Date: Mon, 30 Sep 2024 13:31:56 +0000	[thread overview]
Message-ID: <MW6PR11MB8309C6F94B7A587A150C863F92762@MW6PR11MB8309.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20240906141127.628873-1-bruce.richardson@intel.com>

> The AVX-512 copy code in multiple drivers was incorrect for 32-bit as it
> assumed that each pointer was always 8B in size.
> 
> Bruce Richardson (4):
>   net/i40e: fix AVX-512 pointer copy on 32-bit
>   net/ice: fix AVX-512 pointer copy on 32-bit
>   net/iavf: fix AVX-512 pointer copy on 32-bit
>   common/idpf: fix AVX-512 pointer copy on 32-bit
> 
>  drivers/common/idpf/idpf_common_rxtx_avx512.c | 7 +++++++
>  drivers/net/i40e/i40e_rxtx_vec_avx512.c       | 7 +++++++
>  drivers/net/iavf/iavf_rxtx_vec_avx512.c       | 7 +++++++
>  drivers/net/ice/ice_rxtx_vec_avx512.c         | 7 +++++++

Series looks good to me.

Series-acked-by: Ian Stokes <ian.stokes@intel.com>



  parent reply	other threads:[~2024-09-30 13:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-06 14:11 Bruce Richardson
2024-09-06 14:11 ` [PATCH 1/4] net/i40e: fix AVX-512 pointer copy " Bruce Richardson
2024-09-30 13:27   ` Stokes, Ian
2024-09-06 14:11 ` [PATCH 2/4] net/ice: " Bruce Richardson
2024-09-30 13:29   ` Stokes, Ian
2024-09-06 14:11 ` [PATCH 3/4] net/iavf: " Bruce Richardson
2024-09-06 14:11 ` [PATCH 4/4] common/idpf: " Bruce Richardson
2024-09-30 13:31 ` Stokes, Ian [this message]
2024-09-30 15:38 ` [PATCH 0/4] fix issues with using AVX-512 drivers " David Marchand
2024-09-30 15:57   ` Bruce Richardson
2024-09-30 17:52     ` Bruce Richardson

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=MW6PR11MB8309C6F94B7A587A150C863F92762@MW6PR11MB8309.namprd11.prod.outlook.com \
    --to=ian.stokes@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@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).