public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Ciara Loftus <ciara.loftus@intel.com>
To: dev@dpdk.org
Cc: Ciara Loftus <ciara.loftus@intel.com>, stable@dpdk.org
Subject: [PATCH] net/i40e: fix simple Tx prepare rejecting tunnel type flags
Date: Fri, 20 Mar 2026 11:14:59 +0000	[thread overview]
Message-ID: <20260320111459.1396374-1-ciara.loftus@intel.com> (raw)

The tunnel type bits in ol_flags (RTE_MBUF_F_TX_TUNNEL_*) identify
the encapsulation protocol used by a packet. An application may set
these to indicate tunnel type without requesting any tunnel offload.
The simple Tx path was incorrectly treating these flags as unsupported
offload requests and rejecting the packet.

Add RTE_MBUF_F_TX_TUNNEL_MASK to the set of permitted flags in the
simple Tx supported offloads mask to permit tunnel flags in the mbuf.

Bugzilla ID: 1342
Fixes: 146ffa81d05e ("net/i40e: add Tx preparation for simple Tx datapath")
Cc: stable@dpdk.org

Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
---
 drivers/net/intel/i40e/i40e_rxtx.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/net/intel/i40e/i40e_rxtx.c b/drivers/net/intel/i40e/i40e_rxtx.c
index c5ac75e0f0..a2b351e932 100644
--- a/drivers/net/intel/i40e/i40e_rxtx.c
+++ b/drivers/net/intel/i40e/i40e_rxtx.c
@@ -74,7 +74,8 @@
 #define I40E_TX_OFFLOAD_SIMPLE_SUP_MASK (RTE_MBUF_F_TX_IPV4 | \
 		RTE_MBUF_F_TX_IPV6 | \
 		RTE_MBUF_F_TX_OUTER_IPV4 | \
-		RTE_MBUF_F_TX_OUTER_IPV6)
+		RTE_MBUF_F_TX_OUTER_IPV6 | \
+		RTE_MBUF_F_TX_TUNNEL_MASK)
 
 #define I40E_TX_OFFLOAD_SIMPLE_NOTSUP_MASK \
 		(RTE_MBUF_F_TX_OFFLOAD_MASK ^ I40E_TX_OFFLOAD_SIMPLE_SUP_MASK)
-- 
2.43.0


             reply	other threads:[~2026-03-20 11:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 11:14 Ciara Loftus [this message]
2026-04-03 13:36 ` [PATCH] net/i40e: fix simple Tx prepare rejecting tunnel type flags 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=20260320111459.1396374-1-ciara.loftus@intel.com \
    --to=ciara.loftus@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@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