From: David Ahern <dsahern@kernel.org>
To: Richard Gobert <richardbgobert@gmail.com>,
davem@davemloft.net, 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 v2 1/3] net: gso: add HBH extension header offload support
Date: Tue, 2 Jan 2024 09:22:54 -0700 [thread overview]
Message-ID: <e29255b4-4905-4c33-82b8-094c7b8ef61d@kernel.org> (raw)
In-Reply-To: <27d4cc21-1ce5-4417-bd0c-6dd43a92e4aa@gmail.com>
On 1/2/24 6:20 AM, Richard Gobert wrote:
> This commit adds net_offload to IPv6 Hop-by-Hop extension headers (as it
> is done for routing and dstopts) since it is supported in GSO and GRO.
> This allows to remove specific HBH conditionals in GSO and GRO when
> pulling and parsing an incoming packet.
>
> Signed-off-by: Richard Gobert <richardbgobert@gmail.com>
> Reviewed-by: Willem de Bruijn <willemb@google.com>
> ---
> net/ipv6/exthdrs_offload.c | 11 +++++++++++
> net/ipv6/ip6_offload.c | 25 +++++++++++--------------
> 2 files changed, 22 insertions(+), 14 deletions(-)
>
Reviewed-by: David Ahern <dsahern@kernel.org>
next prev parent reply other threads:[~2024-01-02 16:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 13:15 [PATCH net-next v2 0/3] net: gro: reduce extension header parsing overhead Richard Gobert
2024-01-02 13:20 ` [PATCH net-next v2 1/3] net: gso: add HBH extension header offload support Richard Gobert
2024-01-02 16:22 ` David Ahern [this message]
2024-01-02 17:17 ` Eric Dumazet
2024-01-02 13:24 ` [PATCH net-next v2 2/3] net: gro: parse ipv6 ext headers without frag0 invalidation Richard Gobert
2024-01-02 16:33 ` David Ahern
2024-01-02 17:33 ` Eric Dumazet
2024-01-03 13:08 ` Richard Gobert
2024-01-03 13:30 ` Eric Dumazet
2024-01-03 14:01 ` Richard Gobert
2024-01-02 13:28 ` [PATCH net-next v2 3/3] selftests/net: fix GRO coalesce test and add ext header coalesce tests Richard Gobert
2024-01-02 15:09 ` Willem de Bruijn
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=e29255b4-4905-4c33-82b8-094c7b8ef61d@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).