From: patchwork-bot+netdevbpf@kernel.org
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
dsahern@gmail.com, nikolay@nvidia.com, idosch@idosch.org
Subject: Re: [PATCH net-next] net: nexthop: reduce rcu synchronizations when replacing resilient groups
Date: Tue, 30 Nov 2021 12:10:10 +0000 [thread overview]
Message-ID: <163827421070.23105.15957891178793599366.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211129120924.461545-1-razor@blackwall.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 29 Nov 2021 14:09:24 +0200 you wrote:
> From: Nikolay Aleksandrov <nikolay@nvidia.com>
>
> We can optimize resilient nexthop group replaces by reducing the number of
> synchronize_net calls. After commit 1005f19b9357 ("net: nexthop: release
> IPv6 per-cpu dsts when replacing a nexthop group") we always do a
> synchronize_net because we must ensure no new dsts can be created for the
> replaced group's removed nexthops, but we already did that when replacing
> resilient groups, so if we always call synchronize_net after any group
> type replacement we'll take care of both cases and reduce synchronize_net
> calls for resilient groups.
>
> [...]
Here is the summary with links:
- [net-next] net: nexthop: reduce rcu synchronizations when replacing resilient groups
https://git.kernel.org/netdev/net-next/c/7709efa62c4f
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-30 12:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 12:09 [PATCH net-next] net: nexthop: reduce rcu synchronizations when replacing resilient groups Nikolay Aleksandrov
2021-11-29 14:29 ` Ido Schimmel
2021-11-29 15:32 ` David Ahern
2021-11-30 12:10 ` 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=163827421070.23105.15957891178793599366.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=idosch@idosch.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=razor@blackwall.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