On Thu, Feb 05, 2026 at 12:46:18PM +0000, Ciara Loftus wrote:
> Commit 258f346f5d5e ("net/i40e: use same Rx path across processes")
> changed the way that secondary processes selected their Rx burst
> function. Instead of letting secondary processes select their own
> function, they now used the function selected by the primary process.
> However, the primary process only selects the function at device start,
> so if the primary process hadn't started the device by the time the
> secondary process was selecting its Rx burst function, the secondary
> process would not select the correct function.
>
> This commit addresses this issue by allowing the secondary process to
> select the path if the device has not been started yet.
>
> Fixes: 258f346f5d5e ("net/i40e: use same Rx path across processes")
> Cc: [email protected]
>
> Signed-off-by: Ciara Loftus <[email protected]>
> ---
> drivers/net/intel/i40e/i40e_rxtx.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/intel/i40e/i40e_rxtx.c
> b/drivers/net/intel/i40e/i40e_rxtx.c
> index 1c3586778c..3deeff165d 100644
> --- a/drivers/net/intel/i40e/i40e_rxtx.c
> +++ b/drivers/net/intel/i40e/i40e_rxtx.c
> @@ -3494,8 +3494,8 @@ i40e_set_rx_function(struct rte_eth_dev *dev)
> uint16_t i;
> enum rte_vect_max_simd rx_simd_width = i40e_get_max_simd_bitwidth();
>
> - /* The primary process selects the rx path for all processes. */
> - if (rte_eal_process_type() != RTE_PROC_PRIMARY)
> + /* If the device has started the function has already been selected. */
> + if (dev->data->dev_started)
> goto out;
>
There is no atomic ops or mutual exclusion here, so what happens if two
processes both call this function at the same time? Do both just get the
same result or do we end up with some conflicts?
