DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: vipin.varghese@amd.com, Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH] doc/dmadevs: add note clarifying naming of idxd devices
Date: Tue, 25 Jul 2023 17:16:29 +0100	[thread overview]
Message-ID: <20230725161629.307093-1-bruce.richardson@intel.com> (raw)

Since the test-dma-perf application identifies devices by name, include
in the idxd driver documentation a note on device naming when vfio-pci.
See also discussion in bugzilla[1].

[1] https://bugs.dpdk.org/show_bug.cgi?id=1268

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
 doc/guides/dmadevs/idxd.rst | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/doc/guides/dmadevs/idxd.rst b/doc/guides/dmadevs/idxd.rst
index ea101031bf..a9a788ac56 100644
--- a/doc/guides/dmadevs/idxd.rst
+++ b/doc/guides/dmadevs/idxd.rst
@@ -123,6 +123,13 @@ For example::
 
 	$ dpdk-devbind.py -b vfio-pci 6a:01.0
 
+.. note::
+
+  Since each individual queue on the HW device is its own separate dmadev instance,
+  the internal DMA device name includes the HW queue id as a suffix on the PCI id.
+  The above device when used by a DPDK application will be accessible via dmadevs with names:
+  ``0000:6a:01.0-q0``, ``00006a:01.0-q1``, etc.
+
 Device Probing and Initialization
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- 
2.39.2


             reply	other threads:[~2023-07-25 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 16:16 Bruce Richardson [this message]
2023-07-25 16:18 ` Bruce Richardson
2023-07-26  0:51   ` Varghese, Vipin
2023-07-27 21:55     ` Thomas Monjalon

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=20230725161629.307093-1-bruce.richardson@intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=vipin.varghese@amd.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;
as well as URLs for NNTP newsgroup(s).