From: "Ji, Kai" <kai.ji@intel.com>
To: "Finn, Emma" <emma.finn@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [v2] doc: update device configuration in qat guide
Date: Wed, 17 Dec 2025 09:22:11 +0000 [thread overview]
Message-ID: <SA3PR11MB74617FD778283A8863CDFB3181ABA@SA3PR11MB7461.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20251215104109.1476713-1-emma.finn@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2032 bytes --]
Acked-by: Kai Ji <kai.ji@intel.com>
________________________________
From: Finn, Emma <emma.finn@intel.com>
Sent: 15 December 2025 10:41
To: Ji, Kai <kai.ji@intel.com>
Cc: dev@dpdk.org <dev@dpdk.org>; Finn, Emma <emma.finn@intel.com>
Subject: [v2] doc: update device configuration in qat guide
Added note for QAT driver information and device
configuration for services.
Signed-off-by: Emma Finn <emma.finn@intel.com>
---
doc/guides/cryptodevs/qat.rst | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/doc/guides/cryptodevs/qat.rst b/doc/guides/cryptodevs/qat.rst
index 68d792e4cc..bae7724a76 100644
--- a/doc/guides/cryptodevs/qat.rst
+++ b/doc/guides/cryptodevs/qat.rst
@@ -501,6 +501,27 @@ If you are running on a kernel which includes a driver for your device, see
The actual crypto services enabled on the system depend
on QAT driver capabilities and hardware slice configuration.
+..note::
+
+ With the introduction of QAT Generation 4, the in-tree drivers are available within the
+ mainline Linux kernel. Out-of-tree (OOT) drivers for QAT Gen 4 are currently in sustaining
+ mode, meaning they will only receive maintenance updates without new feature development.
+ Future generations of QAT will be supported with in-tree drivers exclusively.
+
+.. note::
+
+ For **in-tree drivers**, when multiple QAT instances are available, each instance is assigned a
+ different crypto service by default (asym;sym or dc). The available crypto queue pair request
+ will return zero if the corresponding service is not enabled.
+
+ To verify the device configuration, run:
+ cat /sys/bus/pci/devices/<BDF>/qat/cfg_services
+
+ For symmetric and asymmetric crypto services, ensure that `"asym;sym"` are enabled.
+ For **out-of-tree drivers**, the configuration file for each instance can be found at:
+ /etc/<GEN>_dev<ID>.conf
+
+
Installation using kernel.org driver
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
2.43.0
[-- Attachment #2: Type: text/html, Size: 3305 bytes --]
prev parent reply other threads:[~2025-12-17 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 13:47 [PATCH] " Emma Finn
2025-12-15 10:41 ` [v2] " Emma Finn
2025-12-17 9:22 ` Ji, Kai [this message]
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=SA3PR11MB74617FD778283A8863CDFB3181ABA@SA3PR11MB7461.namprd11.prod.outlook.com \
--to=kai.ji@intel.com \
--cc=dev@dpdk.org \
--cc=emma.finn@intel.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).