public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Shani Peretz <shperetz@nvidia.com>
To: <dev@dpdk.org>
Cc: <rasland@nvidia.com>, <michaelba@nvidia.com>,
	Shani Peretz <shperetz@nvidia.com>,
	Dariusz Sosnowski <dsosnowski@nvidia.com>,
	"Viacheslav Ovsiienko" <viacheslavo@nvidia.com>,
	Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Subject: [PATCH] platform/mlx5: clarify device FD closure in mlx5 guide
Date: Tue, 10 Feb 2026 16:46:53 +0200	[thread overview]
Message-ID: <20260210144654.96538-1-shperetz@nvidia.com> (raw)

Document that PMD takes ownership of the duplicated cmd_fd
and closes it during device teardown.

Signed-off-by: Shani Peretz <shperetz@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
---
 doc/guides/platform/mlx5.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/doc/guides/platform/mlx5.rst b/doc/guides/platform/mlx5.rst
index f386980fdd..285d58be4f 100644
--- a/doc/guides/platform/mlx5.rst
+++ b/doc/guides/platform/mlx5.rst
@@ -710,6 +710,7 @@ and below are the arguments supported by the common mlx5 layer.
   File descriptor of ``ibv_context`` created outside the PMD.
   PMD will use this FD to import remote CTX. The ``cmd_fd`` is obtained from
   the ``ibv_context->cmd_fd`` member, which must be dup'd before being passed.
+  The PMD closes the duplicated FD when the device is closed.
   This parameter is valid only if ``pd_handle`` parameter is specified.
 
   By default, the PMD will create a new ``ibv_context``.
-- 
2.34.1


             reply	other threads:[~2026-02-10 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 14:46 Shani Peretz [this message]
2026-02-24 12:11 ` [PATCH] platform/mlx5: clarify device FD closure in mlx5 guide Raslan Darawsheh

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=20260210144654.96538-1-shperetz@nvidia.com \
    --to=shperetz@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=michaelba@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --cc=viacheslavo@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