From: Alice Mikityanska <alice.projects@fastmail.im>
To: Daniel Borkmann <daniel@iogearbox.net>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Xin Long <lucien.xin@gmail.com>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
David Ahern <dsahern@kernel.org>,
Nikolay Aleksandrov <razor@blackwall.org>
Cc: Shuah Khan <shuah@kernel.org>,
Stanislav Fomichev <stfomichev@gmail.com>,
netdev@vger.kernel.org, Alice Mikityanska <alice@isovalent.com>
Subject: [PATCH net-next v3 07/11] ice: Remove jumbo_remove step from TX path
Date: Mon, 2 Feb 2026 21:23:34 +0200 [thread overview]
Message-ID: <20260202192338.2373930-8-alice.projects@fastmail.im> (raw)
In-Reply-To: <20260202192338.2373930-1-alice.projects@fastmail.im>
From: Alice Mikityanska <alice@isovalent.com>
Now that the kernel doesn't insert HBH for BIG TCP IPv6 packets, remove
unnecessary steps from the ice TX path, that used to check and remove
HBH.
Signed-off-by: Alice Mikityanska <alice@isovalent.com>
Acked-by: Paolo Abeni <pabeni@redhat.com>
---
drivers/net/ethernet/intel/ice/ice_txrx.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/net/ethernet/intel/ice/ice_txrx.c b/drivers/net/ethernet/intel/ice/ice_txrx.c
index 396326a6d5be..6fa201a14f51 100644
--- a/drivers/net/ethernet/intel/ice/ice_txrx.c
+++ b/drivers/net/ethernet/intel/ice/ice_txrx.c
@@ -2156,9 +2156,6 @@ ice_xmit_frame_ring(struct sk_buff *skb, struct ice_tx_ring *tx_ring)
ice_trace(xmit_frame_ring, tx_ring, skb);
- if (unlikely(ipv6_hopopt_jumbo_remove(skb)))
- goto out_drop;
-
count = ice_xmit_desc_count(skb);
if (ice_chk_linearize(skb, count)) {
if (__skb_linearize(skb))
--
2.52.0
next prev parent reply other threads:[~2026-02-02 19:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 19:23 [PATCH net-next v3 00/11] BIG TCP without HBH in IPv6 Alice Mikityanska
2026-02-02 19:23 ` [PATCH net-next v3 01/11] net/ipv6: Introduce payload_len helpers Alice Mikityanska
2026-02-02 19:23 ` [PATCH net-next v3 02/11] net/ipv6: Drop HBH for BIG TCP on TX side Alice Mikityanska
2026-02-02 19:23 ` [PATCH net-next v3 03/11] net/ipv6: Drop HBH for BIG TCP on RX side Alice Mikityanska
2026-02-02 19:23 ` [PATCH net-next v3 04/11] net/ipv6: Remove jumbo_remove step from TX path Alice Mikityanska
2026-02-02 19:23 ` [PATCH net-next v3 05/11] net/mlx5e: " Alice Mikityanska
2026-02-02 19:23 ` [PATCH net-next v3 06/11] net/mlx4: " Alice Mikityanska
2026-02-02 19:23 ` Alice Mikityanska [this message]
2026-02-02 19:23 ` [PATCH net-next v3 08/11] bnxt_en: " Alice Mikityanska
2026-02-02 22:57 ` Michael Chan
2026-02-02 19:23 ` [PATCH net-next v3 09/11] gve: " Alice Mikityanska
2026-02-02 19:23 ` [PATCH net-next v3 10/11] net: mana: " Alice Mikityanska
2026-02-02 19:23 ` [PATCH net-next v3 11/11] net/ipv6: Remove HBH helpers Alice Mikityanska
2026-02-02 19:49 ` [PATCH net-next v3 00/11] BIG TCP without HBH in IPv6 Eric Dumazet
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=20260202192338.2373930-8-alice.projects@fastmail.im \
--to=alice.projects@fastmail.im \
--cc=alice@isovalent.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=shuah@kernel.org \
--cc=stfomichev@gmail.com \
--cc=willemdebruijn.kernel@gmail.com \
/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