From: Mina Almasry <almasrymina@google.com>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: asml.silence@gmail.com, Jens Axboe <axboe@kernel.dk>,
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: Mon, 18 Aug 2025 11:16:44 -0700 [thread overview]
Message-ID: <CAHS8izMiS-OWASmzy4ZKYrgd50Tj92CkUndC+E12drbziZjE+w@mail.gmail.com> (raw)
In-Reply-To: <20250815110401.2254214-4-dtatulea@nvidia.com>
On Fri, Aug 15, 2025 at 4:07 AM Dragos Tatulea <dtatulea@nvidia.com> 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.
>
> Signed-off-by: Dragos Tatulea <dtatulea@nvidia.com>
Looks like a straightforward change. FWIW,
Reviewed-by: Mina Almasry <almasrymina@google.com>
--
Thanks,
Mina
next prev parent reply other threads:[~2025-08-18 18:16 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 [this message]
2025-08-19 16:04 ` Pavel Begunkov
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=CAHS8izMiS-OWASmzy4ZKYrgd50Tj92CkUndC+E12drbziZjE+w@mail.gmail.com \
--to=almasrymina@google.com \
--cc=asml.silence@gmail.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