From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 647CF42F3A; Tue, 25 Jul 2023 18:16:42 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E20EE40A7F; Tue, 25 Jul 2023 18:16:41 +0200 (CEST) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by mails.dpdk.org (Postfix) with ESMTP id 3BA32406A2 for ; Tue, 25 Jul 2023 18:16:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1690301800; x=1721837800; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=qvUxEGC8Fon32R/shBmiD2TA3CxbrrDKKR3T5jg7ACU=; b=MyN7jkfb0heC+Upl0Ph4HyIJW3mtyPwwQJ2NCnYWT3kjgt1D7EEnlHK3 payVDjTvN4prrF7O7YHdxF2BDrWSCFXk61vcxnEEYL/AqGtceHLULFffA 8HJlEkcpFcbmZBQm+WstrY+yXdmJ7eBATNzSq2vIRmAD3vF8bbm1dlM/0 56XvRet/yELWdzUhTBrAK3hiVEC2MoZFdW8gyrQzzKuK8mQJIgnevpVuP PBBmbCL3MzvfGGQJvDmybbdj6FrNHVeV1YsXQbF4MPPpkSCfIjIcRA2EY 64+cHOjbEn2/xLK4ewbGlR5YgdY2L1GICD9aNDRopKKtWKXBj4BHEwJBC A==; X-IronPort-AV: E=McAfee;i="6600,9927,10782"; a="371386265" X-IronPort-AV: E=Sophos;i="6.01,230,1684825200"; d="scan'208";a="371386265" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 25 Jul 2023 09:16:38 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10782"; a="900001789" X-IronPort-AV: E=Sophos;i="6.01,230,1684825200"; d="scan'208";a="900001789" Received: from silpixa00401385.ir.intel.com ([10.237.214.156]) by orsmga005.jf.intel.com with ESMTP; 25 Jul 2023 09:16:37 -0700 From: Bruce Richardson To: dev@dpdk.org Cc: vipin.varghese@amd.com, Bruce Richardson Subject: [PATCH] doc/dmadevs: add note clarifying naming of idxd devices Date: Tue, 25 Jul 2023 17:16:29 +0100 Message-Id: <20230725161629.307093-1-bruce.richardson@intel.com> X-Mailer: git-send-email 2.39.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 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 --- 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