From: patchwork-bot+netdevbpf@kernel•org
To: Eric Dumazet <edumazet@google•com>
Cc: davem@davemloft•net, kuba@kernel•org, pabeni@redhat•com,
netdev@vger•kernel.org, eric.dumazet@gmail•com, dima@arista•com,
paulmck@kernel•org
Subject: Re: [PATCH net-next] tcp: use 2-arg optimal variant of kfree_rcu()
Date: Sat, 03 Dec 2022 05:50:24 +0000 [thread overview]
Message-ID: <167004662452.29967.13612462517553246760.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221202052847.2623997-1-edumazet@google.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel•org>:
On Fri, 2 Dec 2022 05:28:47 +0000 you wrote:
> kfree_rcu(1-arg) should be avoided as much as possible,
> since this is only possible from sleepable contexts,
> and incurr extra rcu barriers.
>
> I wish the 1-arg variant of kfree_rcu() would
> get a distinct name, like kfree_rcu_slow()
> to avoid it being abused.
>
> [...]
Here is the summary with links:
- [net-next] tcp: use 2-arg optimal variant of kfree_rcu()
https://git.kernel.org/netdev/net-next/c/55fb80d518c7
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:[~2022-12-03 5:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 5:28 [PATCH net-next] tcp: use 2-arg optimal variant of kfree_rcu() Eric Dumazet
2022-12-02 7:44 ` Pavan Chebbi
2022-12-02 16:05 ` Dmitry Safonov
2022-12-02 18:34 ` Paul E. McKenney
2022-12-02 23:49 ` Joel Fernandes
2022-12-03 0:03 ` Paul E. McKenney
2022-12-03 0:12 ` Joel Fernandes
2022-12-03 0:16 ` Joel Fernandes
2022-12-03 0:28 ` Joel Fernandes
2022-12-05 11:09 ` Uladzislau Rezki
2022-12-05 13:23 ` Eric Dumazet
2022-12-05 14:59 ` Uladzislau Rezki
2022-12-05 16:58 ` Eric Dumazet
2022-12-05 17:10 ` Uladzislau Rezki
2022-12-03 5:50 ` 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=167004662452.29967.13612462517553246760.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=dima@arista$(echo .)com \
--cc=edumazet@google$(echo .)com \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=paulmck@kernel$(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