Re: [PATCH net-next v3 0/4] selftests/xsk: improve shared-UMEM coverage

["Björn Töpel" <bjorn@kernel.org>]

Maciej Fijalkowski <maciej.fijalkowski@intel.com> writes:

> On Thu, Aug 20, 2026 at 02:29:20PM -0700, Jakub Kicinski wrote:
>> On Thu, 20 Aug 2026 19:53:00 +0200 Maciej Fijalkowski wrote:
>> > On Thu, Aug 20, 2026 at 10:44:19AM -0700, Jakub Kicinski wrote:
>> > > On Thu, 20 Aug 2026 11:35:53 +0200 Paolo Abeni wrote:  
>> > > > ## Form letter - net-next-closed  
>> > > 
>> > > these are bpf patches. Tushar, tools/testing/selftests/bpf is BPF  
>> > 
>> > But AF_XDP is now net target since some time. Should we move the test
>> > suite out of bpf directory then?
>> 
>> True.. but until the move happens it feels a little awkward
>> taking pure ksft/bpf patches via net-next?
>
> CC: Bjorn
>
> We had a talk about potential next steps and what would take to get this
> test suite executed against HW tests. tl;dr version is that some of the
> work is needed to adjust it from infrastructure POV as currently
> xskxceiver runs as a single process with two separate threads and what
> Bjorn was saying we will rather be needing two standalone processes that
> could be used on DUT and packet generator.

Yeah, that matches what I had in mind -- for HW tests, the two endpoints
need to be independently runnable processes. One runs on the DUT, and
the other on the peer/traffic generator. IOW, the existing tool needs to
support such a setup, which is a move awway from the two-thread setup.

I'm still not convinced that this would be this tool, or something else
(new).

Again, restructuring is definitely a follow-up, and should not block the
shared-UMEM work. Also, the move from selftest/bpf can also be handled
separately.


Björn