From patchwork Mon Nov 2 17:45:06 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Bruce Richardson X-Patchwork-Id: 83431 X-Patchwork-Delegate: david.marchand@redhat.com Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 75C11A04E7; Mon, 2 Nov 2020 18:47:36 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E2A262BEA; Mon, 2 Nov 2020 18:46:14 +0100 (CET) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 7430D2BD5 for ; Mon, 2 Nov 2020 18:46:12 +0100 (CET) IronPort-SDR: +7aeVnSvkgivhT8odtx6uKzDyQJgD1lKKVks0ETsTs9qOm+N5k/p+Lesj6TB2QvzggxO34ixN6 DSHrWYx5S0ww== X-IronPort-AV: E=McAfee;i="6000,8403,9793"; a="233092779" X-IronPort-AV: E=Sophos;i="5.77,445,1596524400"; d="scan'208";a="233092779" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Nov 2020 09:46:12 -0800 IronPort-SDR: PEKz6qqXoV/jGlO4uYYyLsHpSaKJbTx3qX+tUUYmWkwCcdgMRRnoyIsQFsbOmjGaohCiC0De0l bvqtW0eyvUqg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,445,1596524400"; d="scan'208";a="336243710" Received: from silpixa00399126.ir.intel.com ([10.237.222.4]) by orsmga002.jf.intel.com with ESMTP; 02 Nov 2020 09:46:10 -0800 From: Bruce Richardson To: dev@dpdk.org Cc: Bruce Richardson , Matan Azrad , Viacheslav Ovsiienko , Rosen Xu , Luca Boccassi , Andrew Rybchenko Date: Mon, 2 Nov 2020 17:45:06 +0000 Message-Id: <20201102174507.1085128-8-bruce.richardson@intel.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20201102174507.1085128-1-bruce.richardson@intel.com> References: <20201102174507.1085128-1-bruce.richardson@intel.com> MIME-Version: 1.0 Subject: [dpdk-dev] [PATCH 7/8] doc: fix driver names in vDPA devices guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Since the built driver filenames have changed in DPDK 20.11, we need to update the driver doc to match. Fixes: a20b2c01a7a1 ("build: standardize component names and defines") Signed-off-by: Bruce Richardson Reviewed-by: David Marchand --- doc/guides/vdpadevs/mlx5.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/guides/vdpadevs/mlx5.rst b/doc/guides/vdpadevs/mlx5.rst index 9a11eefd2c..9d10fee2b6 100644 --- a/doc/guides/vdpadevs/mlx5.rst +++ b/doc/guides/vdpadevs/mlx5.rst @@ -7,7 +7,7 @@ MLX5 vDPA driver ================ The MLX5 vDPA (vhost data path acceleration) driver library -(**librte_pmd_mlx5_vdpa**) provides support for **Mellanox ConnectX-6**, +(**librte_vdpa_mlx5**) provides support for **Mellanox ConnectX-6**, **Mellanox ConnectX-6 Dx** and **Mellanox BlueField** families of 10/25/40/50/100/200 Gb/s adapters as well as their virtual functions (VF) in SR-IOV context. @@ -37,7 +37,7 @@ to get the best performances: - DevX allows to access firmware objects - Direct Rules manages flow steering at low-level hardware layer -Enabling librte_pmd_mlx5_vdpa causes DPDK applications to be linked against +Enabling librte_vdpa_mlx5 causes DPDK applications to be linked against libibverbs. A Mellanox mlx5 PCI device can be probed by either net/mlx5 driver or vdpa/mlx5