From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next] net-procfs: use xarray iterator to implement /proc/net/dev
Date: Wed, 7 Feb 2024 09:55:49 -0800 [thread overview]
Message-ID: <20240207095549.00237661@kernel.org> (raw)
In-Reply-To: <20240207165318.3814525-1-edumazet@google.com>
On Wed, 7 Feb 2024 16:53:18 +0000 Eric Dumazet wrote:
> In commit 759ab1edb56c ("net: store netdevs in an xarray")
> Jakub added net->dev_by_index to map ifindex to netdevices.
>
> We can get rid of the old hash table (net->dev_index_head),
> one patch at a time, if performance is acceptable.
FWIW there was a basic benchmark result in that commit:
#devs | hash | xa | delta
2 | 18.3 | 20.1 | + 9.8%
16 | 18.3 | 20.1 | + 9.5%
64 | 18.3 | 26.3 | +43.8%
128 | 20.4 | 26.3 | +28.6%
256 | 20.0 | 26.4 | +32.1%
1024 | 26.6 | 26.7 | + 0.2%
8192 |541.3 | 33.5 | -93.8%
The microbenchmark scans indexes in order, if the pattern is more
random xa starts to win at 512 devices already. But that's a lot
of devices, in practice.
obviously not a very realistic load, but I wanted to mention that,
in case you were planning to do similar testing. Having
wasted few hours yesterday reimplementing tls fixes Sabrina
already posted makes me hyper-vigilant now about people
repeating work ;)
> This patch removes unpleasant code to something more readable.
>
> As a bonus, /proc/net/dev gets netdevices sorted by their ifindex.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: Jakub Kicinski <kuba@kernel.org>
next prev parent reply other threads:[~2024-02-07 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 16:53 [PATCH net-next] net-procfs: use xarray iterator to implement /proc/net/dev Eric Dumazet
2024-02-07 17:55 ` Jakub Kicinski [this message]
2024-02-09 3:11 ` 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=20240207095549.00237661@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.