From: David Ahern <dsahern@kernel.org>
To: hawk@kernel.org, netdev@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, shuah@kernel.org,
linux-kselftest@vger.kernel.org, ivan@cloudflare.com,
kernel-team@cloudflare.com
Subject: Re: [RFC PATCH net-next 0/4] ipv4/ipv6: local address lookup scaling
Date: Fri, 3 Apr 2026 16:35:17 -0600 [thread overview]
Message-ID: <7ce15a72-1b1e-46fc-999c-e80d77b72c6a@kernel.org> (raw)
In-Reply-To: <20260331210739.3998753-1-hawk@kernel.org>
On 3/31/26 3:07 PM, hawk@kernel.org wrote:
> Benchmarks
> ----------
>
> Performance was measured using bpftrace kprobe/kretprobe on
> __ip_dev_find inside a virtme-ng VM (4 vCPUs, veth pair, network
> namespaces, CPU-isolated host). A C benchmark tool sends unconnected
> UDP packets in a tight loop, cycling through all source addresses to
> exercise the lookup path on every sendto().
>
> __ip_dev_find average latency (bpftrace stats, 5 rounds x 3s):
>
> Addrs rhltable (ns) hlist (ns) Improvement
> ----- ------------- ---------- -----------
> 20 201 200 0%
why 20 as the low end? 1 ipv4, 2 ipv6 would be most common use case. All
of the benchmarking numbers should start there.
> 100 210 218 +4%
> 500 206 234 +12%
> 700 218 237 +8%
> 1000 214 228 +6%
> 2000 231 265 +13%
> 5000 247 335 +26%
>
prev parent reply other threads:[~2026-04-03 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 21:07 [RFC PATCH net-next 0/4] ipv4/ipv6: local address lookup scaling hawk
2026-03-31 21:07 ` [RFC PATCH net-next 1/4] ipv4: make inet_addr_lst hash table size configurable hawk
2026-03-31 21:07 ` [RFC PATCH net-next 2/4] ipv6: make inet6_addr_lst " hawk
2026-03-31 21:07 ` [RFC PATCH net-next 3/4] ipv4: convert inet_addr_lst to rhltable for dynamic resizing hawk
2026-03-31 21:07 ` [RFC PATCH net-next 4/4] selftests: net: add IPv4 address lookup stress test hawk
2026-04-03 22:35 ` David Ahern [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=7ce15a72-1b1e-46fc-999c-e80d77b72c6a@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=ivan@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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