From: patchwork-bot+netdevbpf@kernel•org
To: Richard Gobert <richardbgobert@gmail•com>
Cc: davem@davemloft•net, edumazet@google•com, kuba@kernel•org,
pabeni@redhat•com, yoshfuji@linux-ipv6•org, dsahern@kernel•org,
xeb@mail•ru, roopa@nvidia•com,
eng.alaamohamedsoliman.am@gmail•com, bigeasy@linutronix•de,
heikki.krogerus@linux•intel.com, gregkh@linuxfoundation•org,
iwienand@redhat•com, netdev@vger•kernel.org
Subject: Re: [PATCH V2] net: gro: skb_gro_header helper function
Date: Thu, 25 Aug 2022 08:40:13 +0000 [thread overview]
Message-ID: <166141681399.8929.6193115207084669995.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220823071034.GA56142@debian>
Hello:
This patch was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat•com>:
On Tue, 23 Aug 2022 09:10:49 +0200 you wrote:
> Introduce a simple helper function to replace a common pattern.
> When accessing the GRO header, we fetch the pointer from frag0,
> then test its validity and fetch it from the skb when necessary.
>
> This leads to the pattern
> skb_gro_header_fast -> skb_gro_header_hard -> skb_gro_header_slow
> recurring many times throughout GRO code.
>
> [...]
Here is the summary with links:
- [V2] net: gro: skb_gro_header helper function
https://git.kernel.org/netdev/net-next/c/35ffb6654729
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-08-25 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 7:10 [PATCH V2] net: gro: skb_gro_header helper function Richard Gobert
2022-08-23 16:36 ` Eric Dumazet
2022-08-25 8:40 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-02 14:38 [PATCH v2] " Richard Gobert
2022-08-02 19:28 ` Jakub Kicinski
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=166141681399.8929.6193115207084669995.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=bigeasy@linutronix$(echo .)de \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=eng.alaamohamedsoliman.am@gmail$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=heikki.krogerus@linux$(echo .)intel.com \
--cc=iwienand@redhat$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=richardbgobert@gmail$(echo .)com \
--cc=roopa@nvidia$(echo .)com \
--cc=xeb@mail$(echo .)ru \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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