netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Richard Gobert <richardbgobert@gmail.com>,
	 Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	 netdev@vger.kernel.org,  pabeni@redhat.com,
	 ecree.xilinx@gmail.com
Cc: davem@davemloft.net,  edumazet@google.com,  kuba@kernel.org,
	 horms@kernel.org,  corbet@lwn.net,  saeedm@nvidia.com,
	 tariqt@nvidia.com,  mbloch@nvidia.com,  leon@kernel.org,
	 dsahern@kernel.org,  ncardwell@google.com,  kuniyu@google.com,
	 shuah@kernel.org,  sdf@fomichev.me,
	 aleksander.lobakin@intel.com,  florian.fainelli@broadcom.com,
	 alexander.duyck@gmail.com,  linux-kernel@vger.kernel.org,
	 linux-net-drivers@amd.com
Subject: Re: [PATCH net-next v5 4/5] net: gro: remove unnecessary df checks
Date: Tue, 16 Sep 2025 11:57:26 -0400	[thread overview]
Message-ID: <willemdebruijn.kernel.1fa5cf297a68d@gmail.com> (raw)
In-Reply-To: <4b2c5770-ab53-43f6-8c68-7e2f4a912d8e@gmail.com>

Richard Gobert wrote:
> Willem de Bruijn wrote:
> > Richard Gobert wrote:
> >> Currently, packets with fixed IDs will be merged only if their
> >> don't-fragment bit is set. This restriction is unnecessary since packets
> >> without the don't-fragment bit will be forwarded as-is even if they were
> >> merged together.
> > 
> > Please expand why this is true.
> > 
> > Because either NETIF_F_TSO_MANGLEID is set or segmentation
> > falls back onto software GSO which handles the two FIXEDID
> > variants correctly now, I guess?
> > 
> 
> This is true because the merged packets will be segmented back to
> their original forms before being forwarded. As you already said, the IDs
> will either stay identical or potentially become incrementing if MANGLEID
> is set, either of which is fine.
> 
> >> If packets are merged together and then fragmented, they will first be
> >> re-split into segments before being further fragmented, so the behavior
> >> is identical whether or not the packets were first merged together.
> > 
> > I don't follow this scenario. Fragmentation of a GSO packet after GRO
> > and before GSO?
> > 
> 
> Yes. One could worry that merging packets with the same ID but without DF
> would cause issues if they are then fragmented by the host. What I'm saying
> is that if such packets are merged and then fragmented, they will first be
> segmented back to their original forms by GSO before being further fragmented
> (see ip_finish_output_gso). The fragmentation occurs as if the packets were
> never merged to begin with.

This explicit pointer that fragmentation for such GSO packets happens
in ip_finish_output_gso, which first calls skb_gso_segment, is
informative. It again turns an assertion into an explanation.

I think you jumped the gun a bit on sending a v6 right with these
answers. I'd like these clarifications recorded.

> IOW, fragmentation occurs the same way regardless
> of whether the packets were merged (GRO + GSO is transparent). I thought I'd
> mention this to clarify why this patch doesn't cause any issues.
> 
> >> Clean up the code by removing the unnecessary don't-fragment checks.
> >>
> >> Signed-off-by: Richard Gobert <richardbgobert@gmail.com>
> >> ---
> >>  include/net/gro.h                 | 5 ++---
> >>  net/ipv4/af_inet.c                | 3 ---
> >>  tools/testing/selftests/net/gro.c | 9 ++++-----
> >>  3 files changed, 6 insertions(+), 11 deletions(-)
> >>
> >> diff --git a/include/net/gro.h b/include/net/gro.h
> >> index 6aa563eec3d0..f14b7e88dbef 100644
> >> --- a/include/net/gro.h
> >> +++ b/include/net/gro.h
> >> @@ -448,17 +448,16 @@ static inline int inet_gro_flush(const struct iphdr *iph, const struct iphdr *ip
> >>  	const u32 id2 = ntohl(*(__be32 *)&iph2->id);
> >>  	const u16 ipid_offset = (id >> 16) - (id2 >> 16);
> >>  	const u16 count = NAPI_GRO_CB(p)->count;
> >> -	const u32 df = id & IP_DF;
> >>  
> >>  	/* All fields must match except length and checksum. */
> >> -	if ((iph->ttl ^ iph2->ttl) | (iph->tos ^ iph2->tos) | (df ^ (id2 & IP_DF)))
> >> +	if ((iph->ttl ^ iph2->ttl) | (iph->tos ^ iph2->tos) | ((id ^ id2) & IP_DF))
> >>  		return true;
> >>  
> >>  	/* When we receive our second frame we can make a decision on if we
> >>  	 * continue this flow as an atomic flow with a fixed ID or if we use
> >>  	 * an incrementing ID.
> >>  	 */
> >> -	if (count == 1 && df && !ipid_offset)
> >> +	if (count == 1 && !ipid_offset)
> >>  		NAPI_GRO_CB(p)->ip_fixedid |= 1 << inner;
> >>  
> >>  	return ipid_offset ^ (count * !(NAPI_GRO_CB(p)->ip_fixedid & (1 << inner)));
> >> diff --git a/net/ipv4/af_inet.c b/net/ipv4/af_inet.c
> >> index fc7a6955fa0a..c0542d9187e2 100644
> >> --- a/net/ipv4/af_inet.c
> >> +++ b/net/ipv4/af_inet.c
> >> @@ -1393,10 +1393,7 @@ struct sk_buff *inet_gso_segment(struct sk_buff *skb,
> >>  
> >>  	segs = ERR_PTR(-EPROTONOSUPPORT);
> >>  
> >> -	/* fixed ID is invalid if DF bit is not set */
> >>  	fixedid = !!(skb_shinfo(skb)->gso_type & (SKB_GSO_TCP_FIXEDID << encap));
> >> -	if (fixedid && !(ip_hdr(skb)->frag_off & htons(IP_DF)))
> >> -		goto out;
> >>  
> >>  	if (!skb->encapsulation || encap)
> >>  		udpfrag = !!(skb_shinfo(skb)->gso_type & SKB_GSO_UDP);
> >> diff --git a/tools/testing/selftests/net/gro.c b/tools/testing/selftests/net/gro.c
> >> index d5824eadea10..3d4a82a2607c 100644
> >> --- a/tools/testing/selftests/net/gro.c
> >> +++ b/tools/testing/selftests/net/gro.c
> >> @@ -670,7 +670,7 @@ static void send_flush_id_case(int fd, struct sockaddr_ll *daddr, int tcase)
> >>  		iph2->id = htons(9);
> >>  		break;
> >>  
> >> -	case 3: /* DF=0, Fixed - should not coalesce */
> >> +	case 3: /* DF=0, Fixed - should coalesce */
> >>  		iph1->frag_off &= ~htons(IP_DF);
> >>  		iph1->id = htons(8);
> >>  
> >> @@ -1188,10 +1188,9 @@ static void gro_receiver(void)
> >>  			correct_payload[0] = PAYLOAD_LEN * 2;
> >>  			check_recv_pkts(rxfd, correct_payload, 1);
> >>  
> >> -			printf("DF=0, Fixed - should not coalesce: ");
> >> -			correct_payload[0] = PAYLOAD_LEN;
> >> -			correct_payload[1] = PAYLOAD_LEN;
> >> -			check_recv_pkts(rxfd, correct_payload, 2);
> >> +			printf("DF=0, Fixed - should coalesce: ");
> >> +			correct_payload[0] = PAYLOAD_LEN * 2;
> >> +			check_recv_pkts(rxfd, correct_payload, 1);
> >>  
> >>  			printf("DF=1, 2 Incrementing and one fixed - should coalesce only first 2 packets: ");
> >>  			correct_payload[0] = PAYLOAD_LEN * 2;
> >> -- 
> >> 2.36.1
> >>
> > 
> > 
> 



  reply	other threads:[~2025-09-16 15:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 11:39 [PATCH net-next v5 0/5] net: gso: restore outer ip ids correctly Richard Gobert
2025-09-15 11:39 ` [PATCH net-next v5 1/5] net: gro: remove is_ipv6 from napi_gro_cb Richard Gobert
2025-09-16  0:01   ` Willem de Bruijn
2025-09-15 11:39 ` [PATCH net-next v5 2/5] net: gro: only merge packets with incrementing or fixed outer ids Richard Gobert
2025-09-16  0:05   ` Willem de Bruijn
2025-09-15 11:39 ` [PATCH net-next v5 3/5] net: gso: restore ids of outer ip headers correctly Richard Gobert
2025-09-16  0:26   ` Willem de Bruijn
2025-09-16 13:46     ` Richard Gobert
2025-09-16 15:52       ` Willem de Bruijn
2025-09-18 11:56         ` Richard Gobert
2025-09-15 11:39 ` [PATCH net-next v5 4/5] net: gro: remove unnecessary df checks Richard Gobert
2025-09-16  0:32   ` Willem de Bruijn
2025-09-16 13:53     ` Richard Gobert
2025-09-16 15:57       ` Willem de Bruijn [this message]
2025-09-18 11:59         ` Richard Gobert
2025-09-15 11:39 ` [PATCH net-next v5 5/5] selftests/net: test ipip packets in gro.sh Richard Gobert
2025-09-16  0:34   ` Willem de Bruijn

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=willemdebruijn.kernel.1fa5cf297a68d@gmail.com \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=alexander.duyck@gmail.com \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net-drivers@amd.com \
    --cc=mbloch@nvidia.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardbgobert@gmail.com \
    --cc=saeedm@nvidia.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=tariqt@nvidia.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;
as well as URLs for NNTP newsgroup(s).