From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fiona Trahe Subject: [PATCH v2 6/8] doc/qat: update kernel dependency section Date: Thu, 9 Aug 2018 17:50:28 +0100 Message-ID: <1533833430-29134-7-git-send-email-fiona.trahe@intel.com> References: <1533820674-9507-1-git-send-email-fiona.trahe@intel.com> Cc: fiona.trahe@intel.com To: dev@dpdk.org, pablo.de.lara.guarch@intel.com, tomaszx.jozwiak@intel.com Return-path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 25C344C96 for ; Thu, 9 Aug 2018 18:50:50 +0200 (CEST) In-Reply-To: <1533820674-9507-1-git-send-email-fiona.trahe@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Signed-off-by: Fiona Trahe --- doc/guides/cryptodevs/qat.rst | 12 +++--------- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst index e6d78ac16..2f233ec9d 100644 --- a/doc/guides/cryptodevs/qat.rst +++ b/doc/guides/cryptodevs/qat.rst @@ -120,10 +120,8 @@ Quick instructions are as follows: make -.. _qat_kernel_installation: - Dependency on the QAT kernel driver ------------------------------------ +~~~~~~~~~~~~~~~~~~~~~~~~ To use the QAT PMD an SRIOV-enabled QAT kernel driver is required. The VF devices created and initialised by this driver will be used by the QAT PMD. @@ -132,12 +130,8 @@ Instructions for installation are below, but first an explanation of the relationships between the PF/VF devices and the PMDs visible to DPDK applications. - -Acceleration services - cryptography and compression - are provided to DPDK -applications via PMDs which register to implement the corresponding -cryptodev and compressdev APIs. - -Each QuickAssist VF device can expose one cryptodev PMD and/or one compressdev PMD. +Each QuickAssist PF device exposes a number of VF devices. Each VF device can +enable one cryptodev PMD and/or one compressdev PMD. These QAT PMDs share the same underlying device and pci-mgmt code, but are enumerated independently on their respective APIs and appear as independent devices to applications. -- 2.13.6