From: sashiko-bot@kernel.org
To: "Tariq Toukan" <tariqt@nvidia.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH mlx5-next V2 09/10] RDMA/mlx5: Pull data_direct resource creation in init phase
Date: Wed, 30 Sep 2026 11:56:05 +0000 [thread overview]
Message-ID: <20260930115605.CF5B01F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260930114227.139274-10-tariqt@nvidia.com>
> From: Dragos Tatulea <dtatulea@nvidia.com>
>
> Since data_direct resource creation happens directly after init,
> there's no need to separate them.
>
> This patch moves data direct resource creation in the init phase,
> thus simplifying the data direct API. The cleanup path gets the same
> treatment.
>
> This keeps the existing IB device lifetime and prepares for moving the
> combined initialization and cleanup to mlx5_core load and unload.
>
> The patch has no functional changes.
>
> Signed-off-by: Dragos Tatulea <dtatulea@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930114227.139274-1-tariqt@nvidia.com?part=9
next prev parent reply other threads:[~2026-09-30 11:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 11:42 [PATCH mlx5-next V2 00/10] mlx5: Move data direct infrastructure to mlx5_core Tariq Toukan
2026-09-30 11:42 ` [PATCH mlx5-next V2 01/10] RDMA/mlx5: Notify data direct users via a notifier chain on unbind Tariq Toukan
2026-09-30 11:56 ` sashiko-bot
2026-09-30 11:42 ` [PATCH mlx5-next V2 02/10] RDMA/mlx5: Add mlx5_data_direct_supported() helper Tariq Toukan
2026-09-30 11:56 ` sashiko-bot
2026-09-30 11:42 ` [PATCH mlx5-next V2 03/10] RDMA/mlx5: Make the data direct VUID query self-contained Tariq Toukan
2026-09-30 11:56 ` sashiko-bot
2026-09-30 11:42 ` [PATCH mlx5-next V2 04/10] RDMA/mlx5: Give the data direct PCI driver a proper name Tariq Toukan
2026-09-30 11:55 ` sashiko-bot
2026-09-30 11:42 ` [PATCH mlx5-next V2 05/10] RDMA/mlx5: Move and rename data direct resource functions Tariq Toukan
2026-09-30 11:55 ` sashiko-bot
2026-09-30 11:42 ` [PATCH mlx5-next V2 06/10] RDMA/mlx5: Add new registration stage for data direct users Tariq Toukan
2026-09-30 11:56 ` sashiko-bot
2026-09-30 11:42 ` [PATCH mlx5-next V2 07/10] RDMA/mlx5: Extract IB specific lock out of data direct Tariq Toukan
2026-09-30 11:56 ` sashiko-bot
2026-09-30 11:42 ` [PATCH mlx5-next V2 08/10] RDMA/mlx5: Consolidate data direct state into one object Tariq Toukan
2026-09-30 11:56 ` sashiko-bot
2026-09-30 11:42 ` [PATCH mlx5-next V2 09/10] RDMA/mlx5: Pull data_direct resource creation in init phase Tariq Toukan
2026-09-30 11:56 ` sashiko-bot [this message]
2026-09-30 11:42 ` [PATCH mlx5-next V2 10/10] mlx5: Move data direct implementation to mlx5_core Tariq Toukan
2026-09-30 11:56 ` sashiko-bot
2026-10-01 15:41 ` [PATCH mlx5-next V2 00/10] mlx5: Move data direct infrastructure " 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=20260930115605.CF5B01F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.