From: Ciara Loftus <ciara.loftus@intel.com>
To: dev@dpdk.org
Cc: Ciara Loftus <ciara.loftus@intel.com>
Subject: [PATCH 00/10] Fix multi process path selection in Intel drivers
Date: Thu, 5 Feb 2026 10:29:58 +0000 [thread overview]
Message-ID: <20260205103008.190493-1-ciara.loftus@intel.com> (raw)
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.
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.
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
drivers/net/intel/cpfl/cpfl_rxtx.c | 9 +++++++--
drivers/net/intel/i40e/i40e_rxtx.c | 8 ++++----
drivers/net/intel/iavf/iavf_rxtx.c | 8 ++++----
drivers/net/intel/ice/ice_rxtx.c | 8 ++++----
drivers/net/intel/idpf/idpf_rxtx.c | 9 +++++++--
5 files changed, 26 insertions(+), 16 deletions(-)
--
2.43.0
next reply other threads:[~2026-02-05 10:30 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 10:29 Ciara Loftus [this message]
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 ` [PATCH v3 00/10] Fix multi process path selection in Intel drivers 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=20260205103008.190493-1-ciara.loftus@intel.com \
--to=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