All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Richard Gobert <richardbgobert@gmail.com>
Cc: davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, shuah@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/3] net: gro: reduce extension header parsing overhead
Date: Fri, 05 Jan 2024 16:20:25 +0000	[thread overview]
Message-ID: <170447162551.14252.7658609133386405696.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <ac6fb684-c00e-449c-92c3-99358a927ade@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 3 Jan 2024 15:36:41 +0100 you wrote:
> This series attempts to reduce the parsing overhead of IPv6 extension
> headers in GRO and GSO, by removing extension header specific code and
> enabling the frag0 fast path.
> 
> The following changes were made:
>  - Removed some unnecessary HBH conditionals by adding HBH offload
>    to inet6_offloads
>  - Added a utility function to support frag0 fast path in ipv6_gro_receive
>  - Added selftests for IPv6 packets with extension headers in GRO
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/3] net: gso: add HBH extension header offload support
    https://git.kernel.org/netdev/net-next/c/f2e3fc2158e6
  - [net-next,v3,2/3] net: gro: parse ipv6 ext headers without frag0 invalidation
    https://git.kernel.org/netdev/net-next/c/dff0b0161ad5
  - [net-next,v3,3/3] selftests/net: fix GRO coalesce test and add ext header coalesce tests
    https://git.kernel.org/netdev/net-next/c/4e321d590cec

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-01-05 16:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 14:36 [PATCH net-next v3 0/3] net: gro: reduce extension header parsing overhead Richard Gobert
2024-01-03 14:40 ` [PATCH net-next v3 1/3] net: gso: add HBH extension header offload support Richard Gobert
2024-01-03 14:44 ` [PATCH net-next v3 2/3] net: gro: parse ipv6 ext headers without frag0 invalidation Richard Gobert
2024-01-03 16:46   ` Eric Dumazet
2024-01-03 14:48 ` [PATCH net-next v3 3/3] selftests/net: fix GRO coalesce test and add ext header coalesce tests Richard Gobert
2024-01-05 16:20 ` patchwork-bot+netdevbpf [this message]

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=170447162551.14252.7658609133386405696.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardbgobert@gmail.com \
    --cc=shuah@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.