From: Leon Romanovsky <leon@kernel.org>
To: jgg@ziepe.ca, Yishai Hadas <yishaih@nvidia.com>
Cc: linux-rdma@vger.kernel.org, selvin.xavier@broadcom.com,
kalesh-anakkur.purayil@broadcom.com, chengyou@linux.alibaba.com,
kaishen@linux.alibaba.com, tangchengchang@huawei.com,
huangjunxian6@hisilicon.com, abhijit.gangurde@amd.com,
allen.hubbe@amd.com, longli@microsoft.com,
kotaranov@microsoft.com, mkalderon@marvell.com,
bryan-bt.tan@broadcom.com, vishnu.dasa@broadcom.com,
maorg@nvidia.com
Subject: Re: [PATCH V1 rdma-next 00/15] DMA direction and mlx5 driver correctness fixes
Date: Mon, 28 Sep 2026 08:17:17 -0400 [thread overview]
Message-ID: <179059783727.3916571.17336446430052997316.b4-ty@kernel.org> (raw)
In-Reply-To: <20260915140933.40580-1-yishaih@nvidia.com>
On Tue, 15 Sep 2026 17:09:18 +0300, Yishai Hadas wrote:
> This series contains two independent groups of fixes for the RDMA
> subsystem.
>
> Group 1: DMA direction correctness (patches 1-7).
>
> RDMA drivers have historically mapped all pinned user buffers
> DMA_BIDIRECTIONAL regardless of how the device actually accesses them.
> This group tightens the DMA mapping direction to match the real access
> pattern for each buffer type:
>
> [...]
Applied, thanks!
[01/15] RDMA/erdma: Pin CQ buffer writable to match device DMA write access
https://git.kernel.org/rdma/rdma/c/ba3472ed6718bf
[02/15] RDMA/hns: Pin CQ buffer writable to match device DMA write access
https://git.kernel.org/rdma/rdma/c/ce29f6e741844a
[03/15] RDMA/vmw_pvrdma: Pin QP and SRQ rings writable to match device DMA write access
https://git.kernel.org/rdma/rdma/c/89abac4b60b708
[04/15] RDMA/umem: Reuse ib_umem_get_cq_buf_or_va() for VA-only CQ pinning
https://git.kernel.org/rdma/rdma/c/b577999f6f8dbf
[05/15] RDMA/umem: Support an explicit DMA direction other than DMA_BIDIRECTIONAL
https://git.kernel.org/rdma/rdma/c/2445d74c465ac0
[06/15] RDMA/umem: Map CQ buffers DMA_FROM_DEVICE
https://git.kernel.org/rdma/rdma/c/50b96c3e3feb61
[07/15] RDMA/umem: Derive DMA direction from IB access flags
https://git.kernel.org/rdma/rdma/c/dfc5334af5667e
[08/15] RDMA/mlx5: Fix mlx5_ib_dev_res_init() failure when XRC cap is absent
https://git.kernel.org/rdma/rdma/c/4354ab7a85d1dd
[09/15] RDMA/mlx5: Put resource reference in mlx5_ib_wq_event()
(no commit info)
[10/15] RDMA/mlx5: Set WQ event handler before firmware RQ insertion
https://git.kernel.org/rdma/rdma/c/28c559d1e25de4
[11/15] RDMA/mlx5: Set SRQ event handler before xarray insertion
https://git.kernel.org/rdma/rdma/c/d2aa15620e98dc
[12/15] RDMA/mlx5: Set RQ event handler for raw-packet QP
https://git.kernel.org/rdma/rdma/c/a4fa6497002c80
[13/15] RDMA/mlx5: Set QP event handler before firmware QPC insertion
https://git.kernel.org/rdma/rdma/c/05a078c97eb0bb
[14/15] RDMA/mlx5: Initialize QP/RQ/SQ resource refcount before publishing it
https://git.kernel.org/rdma/rdma/c/829a0e65deff3f
[15/15] RDMA/mlx5: Fix signed integer overflow in EQE qp_srq type shift
https://git.kernel.org/rdma/rdma/c/86959c7d009f60
Best regards,
--
Leon Romanovsky <leon@kernel.org>
next prev parent reply other threads:[~2026-09-28 12:17 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 14:09 [PATCH V1 rdma-next 00/15] DMA direction and mlx5 driver correctness fixes Yishai Hadas
2026-09-15 14:09 ` [PATCH V1 rdma-next 01/15] RDMA/erdma: Pin CQ buffer writable to match device DMA write access Yishai Hadas
2026-09-15 14:22 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 02/15] RDMA/hns: " Yishai Hadas
2026-09-15 14:20 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 03/15] RDMA/vmw_pvrdma: Pin QP and SRQ rings " Yishai Hadas
2026-09-15 14:21 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 04/15] RDMA/umem: Reuse ib_umem_get_cq_buf_or_va() for VA-only CQ pinning Yishai Hadas
2026-09-15 14:21 ` sashiko-bot
2026-09-20 12:24 ` Leon Romanovsky
2026-09-22 7:25 ` Yishai Hadas
2026-09-15 14:09 ` [PATCH V1 rdma-next 05/15] RDMA/umem: Support an explicit DMA direction other than DMA_BIDIRECTIONAL Yishai Hadas
2026-09-15 14:21 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 06/15] RDMA/umem: Map CQ buffers DMA_FROM_DEVICE Yishai Hadas
2026-09-15 14:25 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 07/15] RDMA/umem: Derive DMA direction from IB access flags Yishai Hadas
2026-09-15 14:28 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 08/15] RDMA/mlx5: Fix mlx5_ib_dev_res_init() failure when XRC cap is absent Yishai Hadas
2026-09-15 14:24 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 09/15] RDMA/mlx5: Put resource reference in mlx5_ib_wq_event() Yishai Hadas
2026-09-15 14:25 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 10/15] RDMA/mlx5: Set WQ event handler before firmware RQ insertion Yishai Hadas
2026-09-15 14:30 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 11/15] RDMA/mlx5: Set SRQ event handler before xarray insertion Yishai Hadas
2026-09-15 14:36 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 12/15] RDMA/mlx5: Set RQ event handler for raw-packet QP Yishai Hadas
2026-09-15 14:32 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 13/15] RDMA/mlx5: Set QP event handler before firmware QPC insertion Yishai Hadas
2026-09-15 14:35 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 14/15] RDMA/mlx5: Initialize QP/RQ/SQ resource refcount before publishing it Yishai Hadas
2026-09-15 14:29 ` sashiko-bot
2026-09-15 14:09 ` [PATCH V1 rdma-next 15/15] RDMA/mlx5: Fix signed integer overflow in EQE qp_srq type shift Yishai Hadas
2026-09-15 14:31 ` sashiko-bot
2026-09-28 12:17 ` Leon Romanovsky [this message]
2026-09-28 12:19 ` [PATCH V1 rdma-next 00/15] DMA direction and mlx5 driver correctness fixes Leon Romanovsky
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=179059783727.3916571.17336446430052997316.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=abhijit.gangurde@amd.com \
--cc=allen.hubbe@amd.com \
--cc=bryan-bt.tan@broadcom.com \
--cc=chengyou@linux.alibaba.com \
--cc=huangjunxian6@hisilicon.com \
--cc=jgg@ziepe.ca \
--cc=kaishen@linux.alibaba.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=kotaranov@microsoft.com \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=maorg@nvidia.com \
--cc=mkalderon@marvell.com \
--cc=selvin.xavier@broadcom.com \
--cc=tangchengchang@huawei.com \
--cc=vishnu.dasa@broadcom.com \
--cc=yishaih@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