public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@nbd.name>
To: Eric Dumazet <edumazet@google.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	David Ahern <dsahern@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	willemdebruijn.kernel@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net-next v3 3/6] net: add code for TCP fraglist GRO
Date: Fri, 26 Apr 2024 11:44:02 +0200	[thread overview]
Message-ID: <c0161817-1bf5-4749-a20e-de962b76f651@nbd.name> (raw)
In-Reply-To: <CANn89iL-4CB3-+mMtBQapXV7EaCzOWOU1MRp4X1tUtjaXfbk=Q@mail.gmail.com>

On 26.04.24 09:47, Eric Dumazet wrote:
> On Fri, Apr 26, 2024 at 8:51 AM Felix Fietkau <nbd@nbd.name> 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 c493e95e09a5..ffd6b7a4163a 100644
>> --- a/net/ipv4/tcp_offload.c
>> +++ b/net/ipv4/tcp_offload.c
>> @@ -332,6 +332,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) {
> 
> 
> Please add unlikely() for all NAPI_GRO_CB(p)->is_flist checks added in
> this patch.

Will do, thanks.

- Felix


  reply	other threads:[~2024-04-26  9:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26  6:51 [PATCH v3 net-next v3 0/6] Add TCP fraglist GRO support Felix Fietkau
2024-04-26  6:51 ` [PATCH v3 net-next v3 1/6] net: move skb_gro_receive_list from udp to core Felix Fietkau
2024-04-26  7:33   ` Eric Dumazet
2024-04-26  6:51 ` [PATCH v3 net-next v3 2/6] net: add support for segmenting TCP fraglist GSO packets Felix Fietkau
2024-04-26  7:44   ` Eric Dumazet
2024-04-26  9:28     ` Felix Fietkau
2024-04-26  8:28   ` Paolo Abeni
2024-04-26  9:39     ` Felix Fietkau
2024-04-26 10:40       ` Paolo Abeni
2024-04-26 11:35         ` Felix Fietkau
2024-04-26  6:51 ` [PATCH v3 net-next v3 3/6] net: add code for TCP fraglist GRO Felix Fietkau
2024-04-26  7:47   ` Eric Dumazet
2024-04-26  9:44     ` Felix Fietkau [this message]
2024-04-26  8:21   ` Paolo Abeni
2024-04-26  9:41     ` Felix Fietkau
2024-04-26  6:51 ` [PATCH v3 net-next v3 4/6] net: create tcp_gro_lookup helper function Felix Fietkau
2024-04-26  7:25   ` Eric Dumazet
2024-04-26  6:51 ` [PATCH v3 net-next v3 5/6] net: create tcp_gro_header_pull " Felix Fietkau
2024-04-26  7:27   ` Eric Dumazet
2024-04-26  6:51 ` [PATCH v3 net-next v3 6/6] net: add heuristic for enabling TCP fraglist GRO Felix Fietkau
2024-04-26  7:32   ` Eric Dumazet
2024-04-26  9:21     ` 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=c0161817-1bf5-4749-a20e-de962b76f651@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