public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, axboe@kernel.dk
Cc: io-uring@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH iouring] io_uring/zcrx: don't set rx_page_size when not requested
Date: Fri, 27 Feb 2026 19:23:31 +0000	[thread overview]
Message-ID: <148610cd-e0df-4110-a752-b24610c83226@gmail.com> (raw)
In-Reply-To: <20260227170745.2845550-1-kuba@kernel.org>

On 2/27/26 17:07, Jakub Kicinski wrote:
> The rx_buf_len parameter was recently added to the Rx zero-copy
> implementation. The expectation is that when not set system will
> maintain previous behavior and use the default buffer size (PAGE_SIZE).
> 
> This works correctly at the iouring level, but we don't preserve
> the same "zero means default" semantics when registering the memory
> provider on the netdev. mp_param.rx_page_size is unconditionally
> set to PAGE_SIZE. This causes __net_mp_open_rxq() to check for
> QCFG_RX_PAGE_SIZE support in the driver, and return -EOPNOTSUPP
> for drivers that don't advertise it -- even though the user never
> asked for large buffers.
> 
> Only set mp_param.rx_page_size when rx_buf_len was explicitly provided,
> so that the default page size path works on all zcrx-capable drivers.
> mlx5 and fbnic only support 4kB pages in the current release.

Reviewed-by: Pavel Begunkov <asml.silence@gmail.com>

Jens, can you take it into io_uring-7.0?

-- 
Pavel Begunkov


  reply	other threads:[~2026-02-27 19:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-27 17:07 [PATCH iouring] io_uring/zcrx: don't set rx_page_size when not requested Jakub Kicinski
2026-02-27 19:23 ` Pavel Begunkov [this message]
2026-02-27 19:33 ` Jens Axboe

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=148610cd-e0df-4110-a752-b24610c83226@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.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