From: Stanislav Fomichev <stfomichev@gmail.com>
To: "Alexis Lothoré" <alexis.lothore@bootlin.com>
Cc: bpf@vger.kernel.org, "Björn Töpel" <bjorn@kernel.org>,
"Magnus Karlsson" <magnus.karlsson@intel.com>,
"Maciej Fijalkowski" <maciej.fijalkowski@intel.com>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Bastien Curutchet" <bastien.curutchet@bootlin.com>,
"Stanislav Fomichev" <sdf@fomichev.me>,
linux-kselftest@vger.kernel.org
Subject: Re: Question about test_xsk.sh
Date: Thu, 2 Jan 2025 14:30:54 -0800 [thread overview]
Message-ID: <Z3cTnjss5soyUobX@mini-arch> (raw)
In-Reply-To: <e3d0bd36-c074-4cda-b6e1-5f873453ad30@bootlin.com>
On 12/20, Alexis Lothoré wrote:
> Hello all,
>
> I was looking at other test candidates for conversion to bpf test_progs
> framework (to increase automatic testing scope) and found test_xsk.sh, which
> does not seem to have coverage yet in test_progs. This test validates the AF_XDP
> socket behavior with different XDP modes (SKB, DRV, zero copy) and socket
> configuration (normal, busy polling).
>
> The testing program looks pretty big, considering all files involved
> (test_xsk.sh, xskxceiver.c, xsk.c, the different XDP programs) and the matrix of
> tests it runs. So before really diving into it, I would like to ask:
> - is it indeed a good/relevant target for integration in test_progs (all tests
> look like functional tests, so I guess it is) ?
> - if so, is there anyone already working on this ?
> - multiple commits on xskxceiver.c hint that the program is also used for
> testing on real hardware, could someone confirm that it is still the case
> (similar need has been seen with test_xdp_features.sh for example) ? If so, it
> means that the current form must be preserved, and it would be an additional
> integration into test_progs rather a conversion (then most of the code should be
> shared between the non-test_progs and the test_progs version)
Since no one came back to you, here is my attempt to answer.. It is a
good target but it is indeed a good idea to preserve the ability to
run it outside of test_progs framework. Maybe we can eventually run
it with the real hw (in loopback mode) from
tools/testing/selftests/rivers/net/hw. And I don't think anybody
is working on integrating it into test_progs. But Magnus/Maciej should
have more context...
next prev parent reply other threads:[~2025-01-02 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 14:46 Question about test_xsk.sh Alexis Lothoré
2025-01-02 22:30 ` Stanislav Fomichev [this message]
2025-01-03 9:36 ` Magnus Karlsson
2025-01-03 13:52 ` Alexis Lothoré
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=Z3cTnjss5soyUobX@mini-arch \
--to=stfomichev@gmail.com \
--cc=alexis.lothore@bootlin.com \
--cc=andrii@kernel.org \
--cc=bastien.curutchet@bootlin.com \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
/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