From: Jakub Kicinski <kuba@kernel.org>
To: David Wei <dw@davidwei.uk>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
willemb@google.com, petrm@nvidia.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 1/5] selftests: hw-net: auto-disable building the iouring C code
Date: Mon, 24 Nov 2025 18:49:35 -0800 [thread overview]
Message-ID: <20251124184935.6c4ceb3d@kernel.org> (raw)
In-Reply-To: <c8876216-c37d-4d7d-9301-b051273e69b0@davidwei.uk>
On Sat, 22 Nov 2025 16:55:05 -0800 David Wei wrote:
> > +# Check if io_uring supports zero-copy receive
> > +HAS_IOURING_ZCRX := $(shell \
> > + echo -e '#include <liburing.h>\n' \
> > + 'void *func = (void *)io_uring_register_ifq;\n' \
> > + 'int main() {return 0;}' | \
> > + $(CC) -luring -x c - -o /dev/null 2>&1 && echo y)
> > +
> > +ifeq ($(HAS_IOURING_ZCRX),y)
> > +COND_GEN_FILES += iou-zcrx
> > +else
> > +$(warning excluding iouring tests, liburing not installed or too old)
>
> Would you want to mention the min ver needed (2.10)?
I think people would update to latest upstream if they update?
I suspect we'll have to update this check if new dependencies
come up, the version will become stale..
next prev parent reply other threads:[~2025-11-25 2:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 4:02 [PATCH net-next 0/5] selftests: hw-net: toeplitz: read config from the NIC directly Jakub Kicinski
2025-11-21 4:02 ` [PATCH net-next 1/5] selftests: hw-net: auto-disable building the iouring C code Jakub Kicinski
2025-11-23 0:55 ` David Wei
2025-11-25 2:49 ` Jakub Kicinski [this message]
2025-11-21 4:02 ` [PATCH net-next 2/5] selftests: hw-net: toeplitz: make sure NICs have pure Toeplitz configured Jakub Kicinski
2025-11-21 4:02 ` [PATCH net-next 3/5] selftests: hw-net: toeplitz: read the RSS key directly from C Jakub Kicinski
2025-11-23 2:07 ` David Wei
2025-11-21 4:02 ` [PATCH net-next 4/5] selftests: hw-net: toeplitz: read indirection table from the device Jakub Kicinski
2025-11-21 23:12 ` Willem de Bruijn
2025-11-22 1:32 ` Jakub Kicinski
2025-11-22 2:16 ` Willem de Bruijn
2025-11-21 4:02 ` [PATCH net-next 5/5] selftests: hw-net: toeplitz: give the test up to 4 seconds Jakub Kicinski
2025-11-21 23:10 ` [PATCH net-next 0/5] selftests: hw-net: toeplitz: read config from the NIC directly Willem de Bruijn
2025-11-25 3:10 ` 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=20251124184935.6c4ceb3d@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=shuah@kernel.org \
--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).