From fd8036ef7421e56a997f49b66a1116acec246a5c Mon Sep 17 00:00:00 2001 From: Fiona Trahe Date: Thu, 10 Nov 2016 17:27:21 +0000 Subject: [PATCH] doc: add known issue with QAT Issue is with the digest appended feature on QAT PMD. A workaround is also documented. Signed-off-by: Fiona Trahe Acked-by: John McNamara Acked-by: John Griffin --- doc/guides/rel_notes/release_16_11.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/doc/guides/rel_notes/release_16_11.rst b/doc/guides/rel_notes/release_16_11.rst index 365b5a37e2..b54909bd6e 100644 --- a/doc/guides/rel_notes/release_16_11.rst +++ b/doc/guides/rel_notes/release_16_11.rst @@ -213,6 +213,18 @@ Known Issues Therefore, in order to use L3fwd-power, vector mode should be disabled from the config file. +* **Digest address must be supplied for crypto auth operation on QAT PMD.** + + The cryptodev API specifies that if the rte_crypto_sym_op.digest.data field, + and by inference the digest.phys_addr field which points to the same location, + is not set for an auth operation the driver is to understand that the digest + result is located immediately following the region over which the digest is + computed. The QAT PMD doesn't correctly handle this case and reads and writes + to an incorrect location. + + Callers can workaround this by always supplying the digest virtual and + physical address fields in the rte_crypto_sym_op for an auth operation. + API Changes ----------- -- 2.20.1