From: Paolo Abeni <pabeni@redhat.com>
To: Felix Fietkau <nbd@nbd.name>,
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>
Cc: willemdebruijn.kernel@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 net-next v4 2/6] net: add support for segmenting TCP fraglist GSO packets
Date: Tue, 30 Apr 2024 12:40:33 +0200 [thread overview]
Message-ID: <bef0c2839b05d4f2692fa3cde82258e6af87e645.camel@redhat.com> (raw)
In-Reply-To: <9e686cb4-ed1f-4886-a0b7-328367e62757@nbd.name>
On Tue, 2024-04-30 at 12:27 +0200, Felix Fietkau wrote:
> On 30.04.24 12:19, Paolo Abeni wrote:
> > On Sat, 2024-04-27 at 20:22 +0200, 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 | 67 ++++++++++++++++++++++++++++++++++++++++
> > > net/ipv6/tcpv6_offload.c | 58 ++++++++++++++++++++++++++++++++++
> > > 2 files changed, 125 insertions(+)
> > >
> > > diff --git a/net/ipv4/tcp_offload.c b/net/ipv4/tcp_offload.c
> > > index fab0973f995b..affd4ed28cfe 100644
> > > --- a/net/ipv4/tcp_offload.c
> > > +++ b/net/ipv4/tcp_offload.c
> > > @@ -28,6 +28,70 @@ 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)
> > > +{
> > > + const struct tcphdr *th;
> > > + const struct iphdr *iph;
> > > + struct sk_buff *seg;
> > > + struct tcphdr *th2;
> > > + struct iphdr *iph2;
> > > +
> > > + seg = segs;
> > > + th = tcp_hdr(seg);
> > > + iph = ip_hdr(seg);
> > > + th2 = tcp_hdr(seg->next);
> > > + iph2 = ip_hdr(seg->next);
> > > +
> > > + if (!(*(const u32 *)&th->source ^ *(const u32 *)&th2->source) &&
> > > + iph->daddr == iph2->daddr && iph->saddr == iph2->saddr)
> > > + return segs;
> > > +
> > > + while ((seg = seg->next)) {
> > > + th2 = tcp_hdr(seg);
> > > + iph2 = ip_hdr(seg);
> > > +
> > > + __tcpv4_gso_segment_csum(seg,
> > > + &iph2->saddr, iph->saddr,
> > > + &th2->source, th->source);
> > > + __tcpv4_gso_segment_csum(seg,
> > > + &iph2->daddr, iph->daddr,
> > > + &th2->dest, th->dest);
> > > + }
> > > +
> > > + return segs;
> > > +}
> >
> > AFAICS, all the above is really alike the UDP side, except for the
> > transport header zero csum.
> >
> > What about renaming the udp version of this helpers as 'tcpudpv4_...',
> > move them in common code, add an explicit argument for
> > 'zerocsum_allowed' and reuse such helper for both tcp and udp?
> >
> > The same for the ipv6 variant.
>
> Wouldn't that make it more convoluted when taking into account that the
> checksum field offset is different for tcp vs udp?
> How would you handle that?
Probably making a common helper just for
__tcpudpv{4,6}_gso_segment_csum and pass it the target l4 csum pointer
as an additional argument. It would not be spectacularly nice, so no
strong opinion either way.
Cheers,
Paolo
next prev parent reply other threads:[~2024-04-30 10:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240427182305.24461-1-nbd@nbd.name>
2024-04-27 18:22 ` [PATCH v4 net-next v4 1/6] net: move skb_gro_receive_list from udp to core Felix Fietkau
2024-04-27 18:22 ` [PATCH v4 net-next v4 2/6] net: add support for segmenting TCP fraglist GSO packets Felix Fietkau
2024-04-30 10:19 ` Paolo Abeni
2024-04-30 10:27 ` Felix Fietkau
2024-04-30 10:40 ` Paolo Abeni [this message]
2024-04-30 10:57 ` Felix Fietkau
2024-04-30 10:23 ` Paolo Abeni
2024-04-30 11:31 ` Eric Dumazet
2024-04-27 18:22 ` [PATCH v4 net-next v4 3/6] net: add code for TCP fraglist GRO Felix Fietkau
2024-04-27 18:23 ` [PATCH v4 net-next v4 4/6] net: create tcp_gro_lookup helper function Felix Fietkau
2024-04-27 18:23 ` [PATCH v4 net-next v4 5/6] net: create tcp_gro_header_pull " Felix Fietkau
2024-04-27 18:23 ` [PATCH v4 net-next v4 6/6] net: add heuristic for enabling TCP fraglist GRO Felix Fietkau
2024-04-30 3:25 ` Jakub Kicinski
2024-04-30 10:12 ` Paolo Abeni
2024-04-30 10:23 ` Felix Fietkau
2024-04-30 10:31 ` Paolo Abeni
2024-04-30 10:55 ` Felix Fietkau
2024-04-30 11:14 ` Paolo Abeni
2024-04-30 10:33 ` 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=bef0c2839b05d4f2692fa3cde82258e6af87e645.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--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
all inboxes | Powered by JetHome®