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 3/5] net: add code for TCP fraglist GRO
Date: Thu, 25 Apr 2024 17:26:15 +0200	[thread overview]
Message-ID: <13dd8a93-3bfc-4046-ac24-b3e188a53f0e@nbd.name> (raw)
In-Reply-To: <662a746130c38_1e1a1629422@willemb.c.googlers.com.notmuch>

On 25.04.24 17:18, Willem de Bruijn wrote:
> Felix Fietkau wrote:
>> This implements fraglist GRO similar to how it's handled in UDP, however
>> no functional changes are added yet. The next change adds a heuristic for
>> using fraglist GRO instead of regular GRO.
>> 
>> Signed-off-by: Felix Fietkau <nbd@nbd.name>
>> ---
>>  net/ipv4/tcp_offload.c   | 22 ++++++++++++++++++++++
>>  net/ipv6/tcpv6_offload.c |  9 +++++++++
>>  2 files changed, 31 insertions(+)
>> 
>> diff --git a/net/ipv4/tcp_offload.c b/net/ipv4/tcp_offload.c
>> index e455f884190c..68157130c264 100644
>> --- a/net/ipv4/tcp_offload.c
>> +++ b/net/ipv4/tcp_offload.c
>> @@ -336,6 +336,19 @@ struct sk_buff *tcp_gro_receive(struct list_head *head, struct sk_buff *skb)
>>  	flush |= (ntohl(th2->seq) + skb_gro_len(p)) ^ ntohl(th->seq);
>>  	flush |= skb_cmp_decrypted(p, skb);
>>  
>> +	if (NAPI_GRO_CB(p)->is_flist) {
>> +		flush |= (__force int)(flags ^ tcp_flag_word(th2));
> 
> What is the purpose of this check, given the existing check above
> 
>          flush |= (__force int)((flags ^ tcp_flag_word(th2)) &
>                    ~(TCP_FLAG_CWR | TCP_FLAG_FIN | TCP_FLAG_PSH));

The fraglist codepath is not updating the TCP flags of the first packet, 
so the extra check ensures it doesn't have to.

- Felix

  reply	other threads:[~2024-04-25 15:26 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
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 [this message]
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=13dd8a93-3bfc-4046-ac24-b3e188a53f0e@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