From: Dragos Tatulea <dtatulea@nvidia.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Donald Hunter <donald.hunter@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"Pavel Begunkov" <asml.silence@gmail.com>,
Jens Axboe <axboe@kernel.dk>, Shuah Khan <shuah@kernel.org>
Cc: Dragos Tatulea <dtatulea@nvidia.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <io-uring@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>
Subject: [PATCH net-next v2 0/2] netdev: expose page pool order via netlink
Date: Sat, 13 Jun 2026 00:17:02 +0300 [thread overview]
Message-ID: <20260612211709.1456966-2-dtatulea@nvidia.com> (raw)
This small series exposes io_uring's high order page configuration
via the page_pool netlink interface and updates the appropriate
selftest to check this value.
---
v2:
- Switched from exposing page_pool order to rx_buf_len via nl_fill of
the io_uring memory provider.
- Updated selftest to check rx_buf_len.
- v1: https://lore.kernel.org/all/20260611161235.3807332-1-dtatulea@nvidia.com/
---
Dragos Tatulea (2):
netdev: expose io_uring rx_page_order order via netlink
io_uring/zcrx: selftests: verify rx_buf_len for large chunks
Documentation/netlink/specs/netdev.yaml | 9 ++++++-
include/uapi/linux/netdev.h | 2 ++
io_uring/zcrx.c | 8 ++++++
tools/include/uapi/linux/netdev.h | 2 ++
.../selftests/drivers/net/hw/iou-zcrx.py | 26 ++++++++++++++++++-
5 files changed, 45 insertions(+), 2 deletions(-)
--
2.54.0
next reply other threads:[~2026-06-12 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 21:17 Dragos Tatulea [this message]
2026-06-12 21:17 ` [PATCH net-next v2 1/2] netdev: expose io_uring rx_page_order order via netlink Dragos Tatulea
2026-06-12 21:17 ` [PATCH net-next v2 2/2] io_uring/zcrx: selftests: verify rx_buf_len for large chunks Dragos Tatulea
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=20260612211709.1456966-2-dtatulea@nvidia.com \
--to=dtatulea@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=io-uring@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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