From: Eric Dumazet <edumazet@google.com>
To: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
Eric Dumazet <edumazet@google.com>
Subject: [PATCH net-next 0/2] ipv6: optimize rt6_score_route()
Date: Mon, 13 Mar 2023 20:17:30 +0000 [thread overview]
Message-ID: <20230313201732.887488-1-edumazet@google.com> (raw)
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()
drivers/net/vxlan/vxlan_core.c | 4 ++--
include/net/neighbour.h | 2 +-
net/bridge/br_arp_nd_proxy.c | 4 ++--
net/bridge/br_netfilter_hooks.c | 3 ++-
net/core/filter.c | 4 ++--
net/core/neighbour.c | 28 ++++++++++++++--------------
net/ipv4/arp.c | 8 ++++----
net/ipv4/fib_semantics.c | 4 ++--
net/ipv4/nexthop.c | 4 ++--
net/ipv4/route.c | 2 +-
net/ipv6/ip6_output.c | 2 +-
net/ipv6/ndisc.c | 4 ++--
net/ipv6/route.c | 10 +++++-----
13 files changed, 40 insertions(+), 39 deletions(-)
--
2.40.0.rc1.284.g88254d51c5-goog
next reply other threads:[~2023-03-13 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 20:17 Eric Dumazet [this message]
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
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=20230313201732.887488-1-edumazet@google.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--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).