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 3/6] net/iavf: ensure correct conditions for AVX-512 VLAN offload
Date: Thu, 6 Nov 2025 15:09:06 +0000	[thread overview]
Message-ID: <aQy6EvibXbC4jJ5i@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20251106115016.3035639-4-ciara.loftus@intel.com>

On Thu, Nov 06, 2025 at 11:50:13AM +0000, Ciara Loftus wrote:
> Commit 3aa4efa36438 ("net/iavf: support VLAN insertion in AVX512 Tx")
> re-enabled VLAN insertion on the AVX-512 path after it was disabled in
> commit efe1b63775e8 ("net/iavf: fix VLAN insertion in vector path"). The
> initial implementation introduced in commit 4f8259df563a ("net/iavf:
> enable Tx outer checksum offload on AVX512") was inconsistent in that if
> the vlan tag was to be placed in the L2TAG1 field, the offload was only
> performed if IAVF_TX_VLAN_QINQ_OFFLOAD was defined and if the path was
> an offload path. However if the vlan tag was to be placed in the L2TAG2
> field (requiring a context descriptor), the insert was performed
> unconditionally.
> 
> When VLAN insertion was re-enabled, these inconsistencies remained. This
> commit fixes these and ensures the following two conditions are met
> before VLAN insert is offloaded on the AVX-512 path:
> 1. IAVF_TX_VLAN_QINQ_OFFLOAD is defined (defined by default)
> 2. The path is an "offload" path
> 
> Fixes: 3aa4efa36438 ("net/iavf: support VLAN insertion in AVX512 Tx")
> 
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> ---
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

  reply	other threads:[~2025-11-06 15:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 15:22 [PATCH 0/2] Fixes for iavf VLAN insertion offload Ciara Loftus
2025-10-31 15:22 ` [PATCH 1/2] net/iavf: fix AVX-512 double VLAN (QinQ) insertion Ciara Loftus
2025-11-04 17:13   ` Bruce Richardson
2025-11-04 17:16     ` Bruce Richardson
2025-10-31 15:22 ` [PATCH 2/2] net/iavf: fix single VLAN insertion positioning Ciara Loftus
2025-11-04 17:21   ` Bruce Richardson
2025-11-04 17:28     ` Bruce Richardson
2025-11-05 15:26 ` [PATCH v2 0/6] Fixes for iavf VLAN insertion offload Ciara Loftus
2025-11-05 15:26   ` [PATCH v2 1/6] net/iavf: fix compilation with VLAN insertion disabled Ciara Loftus
2025-11-05 19:31     ` Stephen Hemminger
2025-11-05 15:26   ` [PATCH v2 2/6] net/iavf: remove duplication in AVX-512 VLAN insert logic Ciara Loftus
2025-11-05 15:26   ` [PATCH v2 3/6] net/iavf: ensure correct conditions for AVX-512 VLAN offload Ciara Loftus
2025-11-05 15:26   ` [PATCH v2 4/6] net/iavf: fix single VLAN insertion positioning Ciara Loftus
2025-11-05 15:26   ` [PATCH v2 5/6] net/iavf: fix QinQ insertion for single packet Tx Ciara Loftus
2025-11-05 15:26   ` [PATCH v2 6/6] net/iavf: fix QinQ insertion with mbuf flags VLAN and QINQ Ciara Loftus
2025-11-06 11:50   ` [PATCH v3 0/6] Fixes for iavf VLAN insertion offload Ciara Loftus
2025-11-06 11:50     ` [PATCH v3 1/6] net/iavf: fix compilation with VLAN insertion disabled Ciara Loftus
2025-11-06 15:02       ` Bruce Richardson
2025-11-06 11:50     ` [PATCH v3 2/6] net/iavf: remove duplication in AVX-512 VLAN insert logic Ciara Loftus
2025-11-06 15:07       ` Bruce Richardson
2025-11-06 11:50     ` [PATCH v3 3/6] net/iavf: ensure correct conditions for AVX-512 VLAN offload Ciara Loftus
2025-11-06 15:09       ` Bruce Richardson [this message]
2025-11-06 11:50     ` [PATCH v3 4/6] net/iavf: fix single VLAN insertion positioning Ciara Loftus
2025-11-06 15:09       ` Bruce Richardson
2025-11-06 11:50     ` [PATCH v3 5/6] net/iavf: fix QinQ insertion for single packet Tx Ciara Loftus
2025-11-06 15:10       ` Bruce Richardson
2025-11-06 11:50     ` [PATCH v3 6/6] net/iavf: fix QinQ insertion with mbuf flags VLAN and QINQ Ciara Loftus
2025-11-06 15:10       ` Bruce Richardson
2025-11-06 15:32     ` [PATCH v3 0/6] Fixes for iavf VLAN insertion offload 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=aQy6EvibXbC4jJ5i@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).