From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 1DEF84CCDD3 for ; Wed, 30 Sep 2026 11:56:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790769367; cv=none; b=WU+ZerapufDHSGQevcj4mm0j5ui58VrZZ2VxuRJmrjVbF1gVxHI8wVi0a+o+zMMkIAL4xbnYXtmWMey5KnpF0haketLaC98MJdoulWr0rqdKazOwLhM0KEvv8u0G7ixDk7HdPC2cbavXfzqxX6hNPeEP/ffEyywDG6yngro5yNY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790769367; c=relaxed/simple; bh=7xKpkdJrJ80+keemdqHlPbGUbkvVlMij9/gS26NAx6k=; h=From:Subject:To:Cc:In-Reply-To:References:Content-Type:Date: Message-Id; b=kMRVGo9SeDAzA8B2zZZjFDuVt4B4K42QPepmgYL6M2QrLb8RS21qfMJfg1CGTZsUqeoZWws69BG5PVX5FmOEHBRVo0yLXmiBIjhMHB/MS5K//ek1C+95fghmoxRraPPFBkRuxKxo7jKxpN6z9ZVudYWAhJwVc9otq7U3VD3i2+g= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=gJemeZrI; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="gJemeZrI" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CF5B01F00893; Wed, 30 Sep 2026 11:56:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1790769366; bh=7xKpkdJrJ80+keemdqHlPbGUbkvVlMij9/gS26NAx6k=; h=From:Subject:Reply-To:To:Cc:In-Reply-To:References:Date; b=gJemeZrIIdnLQiny9iTIWfQgrNa6fSZcXaZly6DAXnfAAcgMpc+r+JeXegQII7+mD /sxHnLIw3109nP/Wrh7Rlm52yvIflj103QbFt7DZoOPuuYl9jTx4Zjo4aCkGS/q76o NlTbiDzASzMm9UNg5PbAiOnmHvXlatJrmsk9YGEFAfn6fkQ09DEBIxIUCaqF/E7pNE oF7mtsruNNt2YZHlpLZdRrfcr3LXgDnVug5l5rkPEN4ugYUzYzBioSXcwu4284kVJ9 TACvPV0NioU4yR/m97Ls+c2FTxi/V28ASPgVK3xuyRQntUzwLVe1DUzLf4VPmD14vT jCpsH3Yde5kZA== From: sashiko-bot@kernel.org Subject: Re: [PATCH mlx5-next V2 09/10] RDMA/mlx5: Pull data_direct resource creation in init phase Reply-To: sashiko-reviews@lists.linux.dev To: "Tariq Toukan" Cc: linux-rdma@vger.kernel.org In-Reply-To: <20260930114227.139274-10-tariqt@nvidia.com> References: <20260930114227.139274-1-tariqt@nvidia.com> <20260930114227.139274-10-tariqt@nvidia.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Wed, 30 Sep 2026 11:56:05 +0000 Message-Id: <20260930115605.CF5B01F00893@smtp.kernel.org> Precedence: bulk X-Mailing-List: linux-rdma@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: > From: Dragos Tatulea >=20 > Since data_direct resource creation happens directly after init, > there's no need to separate them. >=20 > This patch moves data direct resource creation in the init phase, > thus simplifying the data direct API. The cleanup path gets the same > treatment. >=20 > This keeps the existing IB device lifetime and prepares for moving the > combined initialization and cleanup to mlx5_core load and unload. >=20 > The patch has no functional changes. >=20 > Signed-off-by: Dragos Tatulea > Signed-off-by: Tariq Toukan Sashiko has reviewed this patch and found no issues. It looks great! --=20 Sashiko AI review =C2=B7 https://sashiko.dev/#/patchset/20260930114227.1392= 74-1-tariqt@nvidia.com?part=3D9