From: Jakub Kicinski <kuba@kernel.org>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Donald Hunter <donald.hunter@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Yael Chemla <ychemla@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] netdev: expose page pool order via netlink
Date: Thu, 11 Jun 2026 13:18:49 -0700 [thread overview]
Message-ID: <20260611131849.43870ac5@kernel.org> (raw)
In-Reply-To: <20260611161235.3807332-1-dtatulea@nvidia.com>
On Thu, 11 Jun 2026 19:12:32 +0300 Dragos Tatulea wrote:
> Add a new 'order' attribute to the page-pool netlink interface to expose
> the page pool's allocation order (power of 2 page count).
>
> This adds observability for the latest io_uring rx-buf-len configuration
> for high order pages for zerocopy rx.
>
> The order is added to the queue attribute instead of the nested io_uring
> attribute as it can be useful to see high order page_pools for other
> cases as well.
Memory providers have a callback to populate their own attributes
(nl_fill). Sounds like we should expose rx_buf_len over that thing
instead of exposing the order which is more of a kernel internal?
Also please add checking the new attr to some selftest.
next prev parent reply other threads:[~2026-06-11 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 16:12 [PATCH net-next] netdev: expose page pool order via netlink Dragos Tatulea
2026-06-11 20:18 ` Jakub Kicinski [this message]
2026-06-11 21:18 ` 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=20260611131849.43870ac5@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tariqt@nvidia.com \
--cc=ychemla@nvidia.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