From: Pavel Begunkov <asml.silence@gmail.com>
To: Dragos Tatulea <dtatulea@nvidia.com>,
Parav Pandit <parav@nvidia.com>, Jakub Kicinski <kuba@kernel.org>
Cc: "almasrymina@google.com" <almasrymina@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>,
Cosmin Ratiu <cratiu@nvidia.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC net-next 1/4] net: Allow non parent devices to be used for ZC DMA
Date: Tue, 8 Jul 2025 12:08:48 +0100 [thread overview]
Message-ID: <c006f353-8b35-43c5-b010-d058954ff993@gmail.com> (raw)
In-Reply-To: <22kf5wtxym5x3zllar7ek3onkav6nfzclf7w2lzifhebjme4jb@h4qycdqmwern>
On 7/4/25 14:11, Dragos Tatulea wrote:
> On Thu, Jul 03, 2025 at 01:58:50PM +0200, Parav Pandit wrote:
>>
>>> From: Jakub Kicinski <kuba@kernel.org>
>>> Sent: 03 July 2025 02:23 AM
...>> In an offline discussion, Dragos mentioned that io_uring already
>> operates at the queue level, may be some ideas can be picked up
>> from io_uring?
> The problem for devmem is that the device based API is already set in
> stone so not sure how we can change this. Maybe Mina can chime in.
>
> To sum the conversation up, there are 2 imperfect and overlapping
> solutions:
>
> 1) For the common case of having a single PCI device per netdev, going one
> parent up if the parent device is not DMA capable would be a good
> starting point.
>
> 2) For multi-PF netdev [0], a per-queue get_dma_dev() op would be ideal
> as it provides the right PF device for the given queue. io_uring
> could use this but devmem can't. Devmem could use 1. but the
> driver has to detect and block the multi PF case.
>
> I think we need both. Either that or a netdev op with an optional queue
> parameter. Any thoughts?
No objection from zcrx for either approach, but it sounds like a good
idea to have something simple for 1) sooner than later, and perhaps
marked as a fix.
--
Pavel Begunkov
next prev parent reply other threads:[~2025-07-08 11:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 17:24 [RFC net-next 0/4] devmem/io_uring: Allow devices without parent PCI device Dragos Tatulea
2025-07-02 17:24 ` [RFC net-next 1/4] net: Allow non parent devices to be used for ZC DMA Dragos Tatulea
2025-07-02 18:32 ` Jakub Kicinski
2025-07-02 20:01 ` Dragos Tatulea
2025-07-02 20:53 ` Jakub Kicinski
2025-07-03 11:58 ` Parav Pandit
2025-07-04 13:11 ` Dragos Tatulea
2025-07-07 18:44 ` Mina Almasry
2025-07-07 21:35 ` Dragos Tatulea
2025-07-07 21:55 ` Mina Almasry
2025-07-08 8:52 ` Parav Pandit
2025-07-08 10:47 ` Pavel Begunkov
2025-07-08 14:23 ` Dragos Tatulea
2025-07-08 11:08 ` Pavel Begunkov [this message]
2025-07-08 14:26 ` Dragos Tatulea
2025-07-10 23:58 ` Jakub Kicinski
2025-07-11 2:52 ` Parav Pandit
2025-07-11 13:51 ` Jakub Kicinski
2025-07-08 11:06 ` Pavel Begunkov
2025-07-08 14:10 ` Mina Almasry
2025-07-08 15:25 ` Pavel Begunkov
2025-07-02 17:24 ` [RFC net-next 2/4] io_uring/zcrx: Use the new netdev_get_dma_dev() API Dragos Tatulea
2025-07-02 17:24 ` [RFC net-next 3/4] net: devmem: " Dragos Tatulea
2025-07-02 17:24 ` [RFC net-next 4/4] net/mlx5e: Enable HDS zerocopy flows for SFs 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=c006f353-8b35-43c5-b010-d058954ff993@gmail.com \
--to=asml.silence@gmail.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=saeedm@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;
as well as URLs for NNTP newsgroup(s).