From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
edumazet@google.com
Subject: Re: [PATCH net-next 0/2] gro: remove redundant rcu_read_lock
Date: Thu, 25 Nov 2021 01:30:09 +0000 [thread overview]
Message-ID: <163780380986.5226.16079879965622025793.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211123225608.2155163-1-eric.dumazet@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 23 Nov 2021 14:56:06 -0800 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> Recent trees got an increase of rcu_read_{lock|unlock} costs,
> it is time to get rid of the not needed pairs.
>
> Eric Dumazet (2):
> gro: remove rcu_read_lock/rcu_read_unlock from gro_receive handlers
> gro: remove rcu_read_lock/rcu_read_unlock from gro_complete handlers
>
> [...]
Here is the summary with links:
- [net-next,1/2] gro: remove rcu_read_lock/rcu_read_unlock from gro_receive handlers
https://git.kernel.org/netdev/net-next/c/fc1ca3348a74
- [net-next,2/2] gro: remove rcu_read_lock/rcu_read_unlock from gro_complete handlers
https://git.kernel.org/netdev/net-next/c/627b94f75b82
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-11-25 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 22:56 [PATCH net-next 0/2] gro: remove redundant rcu_read_lock Eric Dumazet
2021-11-23 22:56 ` [PATCH net-next 1/2] gro: remove rcu_read_lock/rcu_read_unlock from gro_receive handlers Eric Dumazet
2021-11-23 22:56 ` [PATCH net-next 2/2] gro: remove rcu_read_lock/rcu_read_unlock from gro_complete handlers Eric Dumazet
2021-11-25 1:30 ` 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=163780380986.5226.16079879965622025793.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.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).