DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Ciara Loftus <ciara.loftus@intel.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] net/i40e: fix supported offloads for Rx vector path
Date: Tue, 2 Sep 2025 10:08:14 +0200	[thread overview]
Message-ID: <CAJFAV8woLUsk=B14RKG+cvOrbdXvGdKaTU59m_A-r_Wkb8KZ6g@mail.gmail.com> (raw)
In-Reply-To: <20250901095953.1858938-1-ciara.loftus@intel.com>

Hello,

On Mon, 1 Sept 2025 at 12:00, Ciara Loftus <ciara.loftus@intel.com> wrote:
>
> The set of supported Rx offloads in the vector path had been defined as
> those supported by the scalar path. This was incorrect so define a new
> list of supported offloads for the vector path. The list is the same
> as the scalar path except it excludes vlan extend and qinq strip.
>
> Fixes: 052ae311091c ("net/i40e: use the common Rx path selection infrastructure")
>
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> ---
>  drivers/net/intel/i40e/i40e_rxtx.h | 11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/intel/i40e/i40e_rxtx.h b/drivers/net/intel/i40e/i40e_rxtx.h
> index 5d5d4e08b0..1f210dfdff 100644
> --- a/drivers/net/intel/i40e/i40e_rxtx.h
> +++ b/drivers/net/intel/i40e/i40e_rxtx.h
> @@ -80,7 +80,16 @@ enum i40e_header_split_mode {
>                 RTE_ETH_RX_OFFLOAD_VLAN_FILTER |        \
>                 RTE_ETH_RX_OFFLOAD_RSS_HASH)
>
> -#define I40E_RX_VECTOR_OFFLOADS I40E_RX_SCALAR_OFFLOADS
> +#define I40E_RX_VECTOR_OFFLOADS (                      \
> +               RTE_ETH_RX_OFFLOAD_VLAN_STRIP |         \
> +               RTE_ETH_RX_OFFLOAD_IPV4_CKSUM |         \
> +               RTE_ETH_RX_OFFLOAD_UDP_CKSUM |          \
> +               RTE_ETH_RX_OFFLOAD_TCP_CKSUM |          \
> +               RTE_ETH_RX_OFFLOAD_OUTER_IPV4_CKSUM |   \
> +               RTE_ETH_RX_OFFLOAD_KEEP_CRC |           \
> +               RTE_ETH_RX_OFFLOAD_SCATTER |            \
> +               RTE_ETH_RX_OFFLOAD_VLAN_FILTER |        \
> +               RTE_ETH_RX_OFFLOAD_RSS_HASH)

I was curious about this fix so I have been trying to understand the
list of supported offloads, and I have a few interrogations.

How does this new code articulate with function
i40e_rx_vec_dev_conf_condition_check_default() (that seems to have a
build check on RTE_LIBRTE_IEEE1588).
This seems like redundant logic to me.

Should the dev_info->rx_offload_capa field be filled with the common
set of flags of the scalar handler?


-- 
David Marchand


  reply	other threads:[~2025-09-02  8:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01  9:59 Ciara Loftus
2025-09-02  8:08 ` David Marchand [this message]
2025-09-02 10:24   ` Loftus, Ciara
2025-09-02 10:48 ` [PATCH v2 0/4] Fixes for net/intel Rx Path Selection Ciara Loftus
2025-09-02 10:48   ` [PATCH v2 1/4] net/i40e: fix supported offloads for Rx vector path Ciara Loftus
2025-09-02 10:48   ` [PATCH v2 2/4] net/i40e: fix vector Rx queue set up logic Ciara Loftus
2025-09-02 10:48   ` [PATCH v2 3/4] net/i40e: remove redundant vector Rx queue setup code Ciara Loftus
2025-09-02 10:48   ` [PATCH v2 4/4] net/iavf: remove duplicate in scalar offload list Ciara Loftus

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='CAJFAV8woLUsk=B14RKG+cvOrbdXvGdKaTU59m_A-r_Wkb8KZ6g@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=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).