From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
dsahern@kernel.org, netdev@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/2] ipv6: optimize rt6_score_route()
Date: Wed, 15 Mar 2023 07:50:18 +0000 [thread overview]
Message-ID: <167886661833.11035.7278696730302666659.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230313201732.887488-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 13 Mar 2023 20:17:30 +0000 you wrote:
> This patch series remove an expensive rwlock acquisition
> in rt6_check_neigh()/rt6_score_route().
>
> First patch adds missing annotations, and second patch implements
> the optimization.
>
> Eric Dumazet (2):
> neighbour: annotate lockless accesses to n->nud_state
> ipv6: remove one read_lock()/read_unlock() pair in rt6_check_neigh()
>
> [...]
Here is the summary with links:
- [net-next,1/2] neighbour: annotate lockless accesses to n->nud_state
https://git.kernel.org/netdev/net-next/c/b071af523579
- [net-next,2/2] ipv6: remove one read_lock()/read_unlock() pair in rt6_check_neigh()
https://git.kernel.org/netdev/net-next/c/c486640aa710
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:[~2023-03-15 7:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 20:17 [PATCH net-next 0/2] ipv6: optimize rt6_score_route() Eric Dumazet
2023-03-13 20:17 ` [PATCH net-next 1/2] neighbour: annotate lockless accesses to n->nud_state Eric Dumazet
2023-03-13 20:45 ` David Ahern
2023-03-13 20:17 ` [PATCH net-next 2/2] ipv6: remove one read_lock()/read_unlock() pair in rt6_check_neigh() Eric Dumazet
2023-03-13 20:46 ` David Ahern
2023-03-14 18:45 ` [PATCH net-next 0/2] ipv6: optimize rt6_score_route() Martin KaFai Lau
2023-03-15 7: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=167886661833.11035.7278696730302666659.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).