From: Stanislav Fomichev <stfomichev@gmail.com>
To: Samiullah Khawaja <skhawaja@google.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"David S . Miller " <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
almasrymina@google.com, willemb@google.com, jdamato@fastly.com,
mkarsten@uwaterloo.ca, netdev@vger.kernel.org
Subject: Re: [RFC PATCH net-next] Add xsk_rr an AF_XDP benchmark to measure latency
Date: Mon, 24 Mar 2025 15:32:47 -0700 [thread overview]
Message-ID: <Z-Hdj_u0-IkYY4ob@mini-arch> (raw)
In-Reply-To: <20250320163523.3501305-1-skhawaja@google.com>
On 03/20, Samiullah Khawaja wrote:
> Note: This is a benchmarking tool that is used for experiments in the
> upcoming v4 of Napi threaded busypoll series. Not intended to be merged.
>
> xsk_rr is a benchmarking tool to measure latency using AF_XDP between
> two nodes. The benchmark can be run with different arguments to simulate
> traffic:
We might want to have something like this, but later, once we have NIPA
runners for vendor NICs. The test would have to live in
tools/testing/selftests/drivers/net/hw, have a python executor to run
it on host/peer and expose the data in some ingestible/trackable format
(so we can mark it red/green depending on the range on the dashboard).
But I might be wrong, having flaky (most of them are) perf tests might not
be super valuable.
next prev parent reply other threads:[~2025-03-24 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 16:35 [RFC PATCH net-next] Add xsk_rr an AF_XDP benchmark to measure latency Samiullah Khawaja
2025-03-24 22:32 ` Stanislav Fomichev [this message]
2025-03-26 21:12 ` Samiullah Khawaja
2025-03-26 22:19 ` Maciej Fijalkowski
2025-03-26 22:32 ` Stanislav Fomichev
2025-03-27 17:08 ` Jakub Kicinski
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=Z-Hdj_u0-IkYY4ob@mini-arch \
--to=stfomichev@gmail.com \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=mkarsten@uwaterloo.ca \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhawaja@google.com \
--cc=willemb@google.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.