public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@nbd.name>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	netdev@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
	"David S. Miller" <davem@davemloft.net>,
	David Ahern <dsahern@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next v2 2/5] net: add support for segmenting TCP fraglist GSO packets
Date: Thu, 25 Apr 2024 17:22:59 +0200	[thread overview]
Message-ID: <89c406c9-9017-49cb-9084-c0a0fc3ad6f3@nbd.name> (raw)
In-Reply-To: <662a73ffea9df_1e1a162941e@willemb.c.googlers.com.notmuch>

On 25.04.24 17:17, Willem de Bruijn wrote:
> Felix Fietkau wrote:
>> Preparation for adding TCP fraglist GRO support. It expects packets to be
>> combined in a similar way as UDP fraglist GSO packets.
>> For IPv4 packets, NAT is handled in the same way as UDP fraglist GSO.
>> 
>> Signed-off-by: Felix Fietkau <nbd@nbd.name>
>> ---
>>  net/ipv4/tcp_offload.c   | 69 ++++++++++++++++++++++++++++++++++++++++
>>  net/ipv6/tcpv6_offload.c |  3 ++
>>  2 files changed, 72 insertions(+)
>> 
>> diff --git a/net/ipv4/tcp_offload.c b/net/ipv4/tcp_offload.c
>> index fab0973f995b..e455f884190c 100644
>> --- a/net/ipv4/tcp_offload.c
>> +++ b/net/ipv4/tcp_offload.c
>> @@ -28,6 +28,72 @@ static void tcp_gso_tstamp(struct sk_buff *skb, unsigned int ts_seq,
>>  	}
>>  }
>>  
>> +static void __tcpv4_gso_segment_csum(struct sk_buff *seg,
>> +				     __be32 *oldip, __be32 *newip,
>> +				     __be16 *oldport, __be16 *newport)
>> +{
>> +	struct tcphdr *th;
>> +	struct iphdr *iph;
>> +
>> +	if (*oldip == *newip && *oldport == *newport)
>> +		return;
>> +
>> +	th = tcp_hdr(seg);
>> +	iph = ip_hdr(seg);
>> +
>> +	inet_proto_csum_replace4(&th->check, seg, *oldip, *newip, true);
>> +	inet_proto_csum_replace2(&th->check, seg, *oldport, *newport, false);
>> +	*oldport = *newport;
>> +
>> +	csum_replace4(&iph->check, *oldip, *newip);
>> +	*oldip = *newip;
>> +}
>> +
>> +static struct sk_buff *__tcpv4_gso_segment_list_csum(struct sk_buff *segs)
>> +{
>> +	struct sk_buff *seg;
>> +	struct tcphdr *th, *th2;
>> +	struct iphdr *iph, *iph2;
>> +	__be32 flags, flags2;
>> +
>> +	seg = segs;
>> +	th = tcp_hdr(seg);
>> +	iph = ip_hdr(seg);
>> +	flags = tcp_flag_word(th);
>> +	flags2 = tcp_flag_word(tcp_hdr(seg->next));
> 
> Vestigial, now that flag overwrite is removed in v2?

Will fix, thanks.

> All this code is very similar to __udpv4_gso_segment_list_csum. But
> the zero checksum handling in __udpv4_gso_segment_csum makes it just
> different enough that I also do not immediately see a straightforward
> way to avoid duplicating.

Also, the checksum field is in a different location in the udp header. I 
don't think avoiding duplication makes sense here.

- Felix

  reply	other threads:[~2024-04-25 15:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 15:04 [PATCH v2 net-next 0/5] Add TCP fraglist GRO support Felix Fietkau
2024-04-25 15:04 ` [PATCH v2 net-next v2 1/5] net: move skb_gro_receive_list from udp to core Felix Fietkau
2024-04-25 15:04 ` [PATCH v2 net-next v2 2/5] net: add support for segmenting TCP fraglist GSO packets Felix Fietkau
2024-04-25 15:17   ` Willem de Bruijn
2024-04-25 15:22     ` Felix Fietkau [this message]
2024-04-25 15:04 ` [PATCH v2 net-next v2 3/5] net: add code for TCP fraglist GRO Felix Fietkau
2024-04-25 15:18   ` Willem de Bruijn
2024-04-25 15:26     ` Felix Fietkau
2024-04-25 15:04 ` [PATCH v2 net-next v2 4/4] net: add heuristic for enabling " Felix Fietkau
2024-04-25 15:04 ` [PATCH v2 net-next v2 4/5] net: create tcp_gro_lookup helper function Felix Fietkau
2024-04-25 15:04 ` [PATCH v2 net-next v2 5/5] net: add heuristic for enabling TCP fraglist GRO Felix Fietkau
2024-04-25 15:26   ` Eric Dumazet
2024-04-25 15:29     ` Felix Fietkau

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=89c406c9-9017-49cb-9084-c0a0fc3ad6f3@nbd.name \
    --to=nbd@nbd.name \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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