DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH v3 00/15] net/intel: rx path selection simplification
Date: Wed, 20 Aug 2025 13:15:20 +0100	[thread overview]
Message-ID: <aKW8WPMhdSXT5SyL@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250818105914.169732-1-ciara.loftus@intel.com>

On Mon, Aug 18, 2025 at 10:58:59AM +0000, Ciara Loftus wrote:
> This series aims to simplify the process of selecting an Rx burst
> function for the i40e, iavf and ice drivers. Three main simplifications
> are made:
> 1. enforcing the same rx burst function for both primary and secondary
> processes.
> 2. using a common function for determining the maximum SIMD width based
> on compiler flags, CPU flags and user-defined limits.
> 3. using a common function for selecting the rx burst function based on
> maximum SIMD width, function features (flex desc, scattered, bulk alloc)
> and requested rx offloads.
> 
> v3:
> * removed arbitrary defines for features and replaced with new sub structure within features
>   structure
> * removed unnecessary initialisation in the path select function
> * added error log for case when tx simd width is invalid in i40e driver
> * fixed ice vector offload mask to excude QINQ
> * removed unnecessary #ifdef CC_AVX512_SUPPORT in ice and i40e driver
> * changed == RTE_VECT_SIMD_256 to >= RTE_VECT_SIMD_256 in ice driver
> 
> Bruce Richardson (1):
>   net/intel: introduce common vector capability function
> 
> Ciara Loftus (14):
>   net/ice: use the same Rx path across process types
>   net/iavf: rename Rx/Tx function type variables
>   net/iavf: use the same Rx path across process types
>   net/i40e: use the same Rx path across process types
>   net/ice: use the new common vector capability function
>   net/iavf: use the new common vector capability function
>   net/i40e: use the new common vector capability function
>   net/iavf: remove redundant field from iavf adapter struct
>   net/ice: remove unsupported Rx offload
>   net/iavf: reorder enum of Rx function types
>   net/intel: introduce infrastructure for Rx path selection
>   net/ice: use the common Rx path selection infrastructure
>   net/iavf: use the common Rx path selection infrastructure
>   net/i40e: use the common Rx path selection infrastructure
> 
Series applied to dpdk-next-net-intel.

Thanks,
/Bruce

      parent reply	other threads:[~2025-08-20 12:15 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 10:58 Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 01/15] net/ice: use the same Rx path across process types Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 02/15] net/iavf: rename Rx/Tx function type variables Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 03/15] net/iavf: use the same Rx path across process types Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 04/15] net/i40e: " Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 05/15] net/intel: introduce common vector capability function Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 06/15] net/ice: use the new " Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 07/15] net/iavf: " Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 08/15] net/i40e: " Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 09/15] net/iavf: remove redundant field from iavf adapter struct Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 10/15] net/ice: remove unsupported Rx offload Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 11/15] net/iavf: reorder enum of Rx function types Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 12/15] net/intel: introduce infrastructure for Rx path selection Ciara Loftus
2025-08-18 10:59 ` [PATCH v3 13/15] net/ice: use the common Rx path selection infrastructure Ciara Loftus
2025-08-20  9:47   ` Bruce Richardson
2025-08-18 10:59 ` [PATCH v3 14/15] net/iavf: " Ciara Loftus
2025-08-20  9:49   ` Bruce Richardson
2025-08-18 10:59 ` [PATCH v3 15/15] net/i40e: " Ciara Loftus
2025-08-20  9:51   ` Bruce Richardson
2025-08-20 12:15 ` Bruce Richardson [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=aKW8WPMhdSXT5SyL@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=ciara.loftus@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).