From: Jakub Kicinski <kuba@kernel.org>
To: Stanislav Fomichev <stfomichev@gmail.com>
Cc: Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
Samiullah Khawaja <skhawaja@google.com>,
"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: Thu, 27 Mar 2025 10:08:53 -0700 [thread overview]
Message-ID: <20250327100853.14bfce4f@kernel.org> (raw)
In-Reply-To: <Z-SAgPijHtVP6S3n@mini-arch>
On Wed, 26 Mar 2025 15:32:32 -0700 Stanislav Fomichev wrote:
> > As you said it's benchmarking tool so I feel like it should land in
> > https://github.com/xdp-project/bpf-examples where we have xdpsock that
> > have been previously used for benchmarks.
>
> I don't think it matters where the tools live. I'm more interested in
> the general guidance on whether we want to continuously run those tools
> on NIPA (on real HW) and track the numbers. Unfortunately it's gonna put
> extra load on the maintainers in terms of tracking and acting on failures,
> but it feels like it's a good direction in general.
I think we should try. Mina is working on merging the page pool test
AFAIU, this is even easier cause it's just user space, no magic modules
to load.
prev parent reply other threads:[~2025-03-27 17:08 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
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 [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=20250327100853.14bfce4f@kernel.org \
--to=kuba@kernel.org \
--cc=almasrymina@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdamato@fastly.com \
--cc=maciej.fijalkowski@intel.com \
--cc=mkarsten@uwaterloo.ca \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=skhawaja@google.com \
--cc=stfomichev@gmail.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 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).