public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Dragos Tatulea <dtatulea@nvidia.com>,
	almasrymina@google.com, Jens Axboe <axboe@kernel.dk>
Cc: cratiu@nvidia.com, tariqt@nvidia.com, parav@nvidia.com,
	Christoph Hellwig <hch@infradead.org>,
	io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC net-next v3 2/7] io_uring/zcrx: add support for custom DMA devices
Date: Tue, 19 Aug 2025 17:04:44 +0100	[thread overview]
Message-ID: <7dd538ed-d767-4c9d-906f-93b9e5341ea6@gmail.com> (raw)
In-Reply-To: <20250815110401.2254214-4-dtatulea@nvidia.com>

On 8/15/25 12:03, Dragos Tatulea wrote:
> Use the new API for getting a DMA device for a specific netdev queue.
> 
> This patch will allow io_uring zero-copy rx to work with devices
> where the DMA device is not stored in the parent device. mlx5 SFs
> are an example of such a device.

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

It'll likely be fine for it to go to the net tree.

-- 
Pavel Begunkov


  parent reply	other threads:[~2025-08-19 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15 11:03 [RFC net-next v3 0/7] devmem/io_uring: allow more flexibility for ZC DMA devices Dragos Tatulea
2025-08-15 11:03 ` [RFC net-next v3 2/7] io_uring/zcrx: add support for custom " Dragos Tatulea
2025-08-18 18:16   ` Mina Almasry
2025-08-19 16:04   ` Pavel Begunkov [this message]
2025-08-15 15:31 ` [RFC net-next v3 0/7] devmem/io_uring: allow more flexibility for ZC " Stanislav Fomichev
2025-08-15 15:48   ` 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=7dd538ed-d767-4c9d-906f-93b9e5341ea6@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=almasrymina@google.com \
    --cc=axboe@kernel.dk \
    --cc=cratiu@nvidia.com \
    --cc=dtatulea@nvidia.com \
    --cc=hch@infradead.org \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parav@nvidia.com \
    --cc=tariqt@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