From: patchwork-bot+netdevbpf@kernel.org
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: almasrymina@google.com, asml.silence@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, axboe@kernel.dk,
saeedm@nvidia.com, tariqt@nvidia.com, mbloch@nvidia.com,
leon@kernel.org, andrew+netdev@lunn.ch, cratiu@nvidia.com,
parav@nvidia.com, netdev@vger.kernel.org, sdf@meta.com,
linux-kernel@vger.kernel.org, io-uring@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v6 0/7] devmem/io_uring: allow more flexibility for ZC DMA devices
Date: Thu, 28 Aug 2025 23:50:16 +0000 [thread overview]
Message-ID: <175642501625.1650971.15574075096463666063.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250827144017.1529208-2-dtatulea@nvidia.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 27 Aug 2025 17:39:54 +0300 you wrote:
> For TCP zerocopy rx (io_uring, devmem), there is an assumption that the
> parent device can do DMA. However that is not always the case:
> - Scalable Function netdevs [1] have the DMA device in the grandparent.
> - For Multi-PF netdevs [2] queues can be associated to different DMA
> devices.
>
> The series adds an API for getting the DMA device for a netdev queue.
> Drivers that have special requirements can implement the newly added
> queue management op. Otherwise the parent will still be used as before.
>
> [...]
Here is the summary with links:
- [net-next,v6,1/7] queue_api: add support for fetching per queue DMA dev
https://git.kernel.org/netdev/net-next/c/13d8e05adf9d
- [net-next,v6,2/7] io_uring/zcrx: add support for custom DMA devices
https://git.kernel.org/netdev/net-next/c/59b8b32ac8d4
- [net-next,v6,3/7] net: devmem: get netdev DMA device via new API
https://git.kernel.org/netdev/net-next/c/7c7e94603a76
- [net-next,v6,4/7] net/mlx5e: add op for getting netdev DMA device
https://git.kernel.org/netdev/net-next/c/f1debf1a2ef4
- [net-next,v6,5/7] net: devmem: pull out dma_dev out of net_devmem_bind_dmabuf
https://git.kernel.org/netdev/net-next/c/512c88fb0e88
- [net-next,v6,6/7] net: devmem: pre-read requested rx queues during bind
https://git.kernel.org/netdev/net-next/c/1b416902cd25
- [net-next,v6,7/7] net: devmem: allow binding on rx queues with same DMA devices
https://git.kernel.org/netdev/net-next/c/b8aab4bb9585
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-08-28 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 14:39 [PATCH net-next v6 0/7] devmem/io_uring: allow more flexibility for ZC DMA devices Dragos Tatulea
2025-08-27 14:39 ` [PATCH net-next v6 2/7] io_uring/zcrx: add support for custom " Dragos Tatulea
2025-08-28 23:50 ` patchwork-bot+netdevbpf [this message]
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=175642501625.1650971.15574075096463666063.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=io-uring@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=sdf@meta.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