public inbox for dev@dpdk.org
 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/10] Fix multi process path selection in Intel drivers
Date: Wed, 18 Feb 2026 12:29:55 +0000	[thread overview]
Message-ID: <aZWwwwUD5e_GO_CF@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260218094937.1652391-1-ciara.loftus@intel.com>

On Wed, Feb 18, 2026 at 09:49:27AM +0000, Ciara Loftus wrote:
> This series fixes and makes consistent the approach to selecting Rx and
> Tx paths in a multi process scenario across the Intel drivers that use
> the common path selection framework.
> 
> In v25.11 the i40e, iavf and ice drivers prevented Rx path selection by
> secondary processes, in favour of simply selecting the path chosen by
> the primary process. However, this model does not work if the primary
> process hasn't started the device before the secondary process
> encounters the path selection logic. To address this, permit path
> selection by any process, so long as the device has not yet been
> started. This allows for the use case where the secondary process is the
> process that starts the device.
> The idpf and cpfl drivers are updated to follow this model as well.
> 
> The same issue exists for the Tx path selection for i40e, iavf, ice,
> idpf and cpfl, so implement the same logic when selecting a Tx path as
> well ie. permit path selection if the device has not been started.
> 
> If two processes were to call the path selection at the same time, in
> most cases they should both land on the same result. Both would be using
> the same information from dev->data to build up the structure that is
> used as input to the path selection function. The effect would be both
> writing the same values to shared variables eg. rx_func_type in
> dev->data->dev_private. For this reason I did not add any locking around
> the path selection logic. The only exception would be the case where the
> primary and secondary processes are configured with different maximum
> SIMD bitwidths however this is an invalid use case IMO.
> 
> I kept the patches for fixing the Rx and Tx path selection separate, as
> the patches that target the Rx side will need to be backported to v25.11
> whereas the patches for the Tx side do not as that logic was introduced
> post v25.11.
> 
> v3: In iavf ensure a secondary process can see if the primary process has
> enabled LLDP, which ensures that the correct Tx path will be chosen ie.
> one with context descriptor support if LLDP is enabled.
> 
> Ciara Loftus (10):
>   net/i40e: permit secondary process Rx path selection
>   net/iavf: permit secondary process Rx path selection
>   net/ice: permit secondary process Rx path selection
>   net/idpf: prevent Rx path selection after device start
>   net/cpfl: prevent Rx path selection after device start
>   net/i40e: permit secondary process Tx path selection
>   net/iavf: permit secondary process Tx path selection
>   net/ice: permit secondary process Tx path selection
>   net/idpf: permit secondary process Tx path selection
>   net/cpfl: permit secondary process Tx path selection
>
Applied to next-net-intel.

I've squashed the final 5 patches together as they are the same changes
just made to different drivers + one other small incidental change for iavf 
The first 5 I've kept all separate as they are also for backporting, and having
them smaller should make that easier.

Thanks,
/Bruce

      parent reply	other threads:[~2026-02-18 12:30 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 10:29 [PATCH 00/10] Fix multi process path selection in Intel drivers Ciara Loftus
2026-02-05 10:29 ` [PATCH 01/10] net/i40e: permit secondary process Rx path selection Ciara Loftus
2026-02-05 10:30 ` [PATCH 02/10] net/iavf: " Ciara Loftus
2026-02-05 10:30 ` [PATCH 03/10] net/ice: " Ciara Loftus
2026-02-05 10:30 ` [PATCH 04/10] net/idpf: prevent Rx path selection after device start Ciara Loftus
2026-02-05 10:30 ` [PATCH 05/10] net/cpfl: " Ciara Loftus
2026-02-05 10:30 ` [PATCH 06/10] net/i40e: permit secondary process Tx path selection Ciara Loftus
2026-02-05 10:30 ` [PATCH 07/10] net/iavf: " Ciara Loftus
2026-02-05 10:30 ` [PATCH 08/10] net/ice: " Ciara Loftus
2026-02-05 10:30 ` [PATCH 09/10] net/idpf: " Ciara Loftus
2026-02-05 10:30 ` [PATCH 10/10] net/cpfl: " Ciara Loftus
2026-02-05 12:46 ` [PATCH v2 00/10] Fix multi process path selection in Intel drivers Ciara Loftus
2026-02-05 12:46   ` [PATCH v2 01/10] net/i40e: permit secondary process Rx path selection Ciara Loftus
2026-02-13 13:15     ` Bruce Richardson
2026-02-17 11:38       ` Loftus, Ciara
2026-02-05 12:46   ` [PATCH v2 02/10] net/iavf: " Ciara Loftus
2026-02-05 12:46   ` [PATCH v2 03/10] net/ice: " Ciara Loftus
2026-02-05 12:46   ` [PATCH v2 04/10] net/idpf: prevent Rx path selection after device start Ciara Loftus
2026-02-05 12:46   ` [PATCH v2 05/10] net/cpfl: " Ciara Loftus
2026-02-05 12:46   ` [PATCH v2 06/10] net/i40e: permit secondary process Tx path selection Ciara Loftus
2026-02-05 12:46   ` [PATCH v2 07/10] net/iavf: " Ciara Loftus
2026-02-05 12:46   ` [PATCH v2 08/10] net/ice: " Ciara Loftus
2026-02-05 12:46   ` [PATCH v2 09/10] net/idpf: " Ciara Loftus
2026-02-05 12:46   ` [PATCH v2 10/10] net/cpfl: " Ciara Loftus
2026-02-18  9:49   ` [PATCH v3 00/10] Fix multi process path selection in Intel drivers Ciara Loftus
2026-02-18  9:49     ` [PATCH v3 01/10] net/i40e: permit secondary process Rx path selection Ciara Loftus
2026-02-18 10:03       ` Bruce Richardson
2026-02-18  9:49     ` [PATCH v3 02/10] net/iavf: " Ciara Loftus
2026-02-18 10:03       ` Bruce Richardson
2026-02-18  9:49     ` [PATCH v3 03/10] net/ice: " Ciara Loftus
2026-02-18 10:04       ` Bruce Richardson
2026-02-18  9:49     ` [PATCH v3 04/10] net/idpf: prevent Rx path selection after device start Ciara Loftus
2026-02-18 10:04       ` Bruce Richardson
2026-02-18  9:49     ` [PATCH v3 05/10] net/cpfl: " Ciara Loftus
2026-02-18 10:05       ` Bruce Richardson
2026-02-18  9:49     ` [PATCH v3 06/10] net/i40e: permit secondary process Tx path selection Ciara Loftus
2026-02-18 10:05       ` Bruce Richardson
2026-02-18  9:49     ` [PATCH v3 07/10] net/iavf: " Ciara Loftus
2026-02-18 10:06       ` Bruce Richardson
2026-02-18  9:49     ` [PATCH v3 08/10] net/ice: " Ciara Loftus
2026-02-18 10:08       ` Bruce Richardson
2026-02-18  9:49     ` [PATCH v3 09/10] net/idpf: " Ciara Loftus
2026-02-18 10:08       ` Bruce Richardson
2026-02-18  9:49     ` [PATCH v3 10/10] net/cpfl: " Ciara Loftus
2026-02-18 10:09       ` Bruce Richardson
2026-02-18 12:29     ` 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=aZWwwwUD5e_GO_CF@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