[dpdk-dev] [PATCH] doc: add known issue on QAT PMD into release notes

2016-11-10 Thread Trahe, Fiona 


> -Original Message-
> From: Trahe, Fiona
> Sent: Thursday, November 10, 2016 4:47 PM
> To: dev at dpdk.org
> Cc: De Lara Guarch, Pablo ; Trahe, Fiona
> ; Griffin, John 
> Subject: [PATCH] doc: add known issue on QAT PMD into release notes
> 
> Issue is with the digest appended feature on QAT PMD.
> A workaround is also documented.
> 
> Signed-off-by: Fiona Trahe 
> ---
Self-nack 
Checkpatch white space errors - will send an update shortly

[dpdk-dev] [PATCH] doc: add known issue on QAT PMD into release notes

2016-11-10 Thread Mcnamara, John 
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Fiona Trahe
> Sent: Thursday, November 10, 2016 4:47 PM
> To: dev at dpdk.org
> Cc: De Lara Guarch, Pablo ; Trahe, Fiona
> ; Griffin, John 
> Subject: [dpdk-dev] [PATCH] doc: add known issue on QAT PMD into release
> notes
> 
> Issue is with the digest appended feature on QAT PMD.
> A workaround is also documented.
> 
> Signed-off-by: Fiona Trahe 

Acked-by: John McNamara

[dpdk-dev] [PATCH] doc: add known issue on QAT PMD into release notes

2016-11-10 Thread Fiona Trahe 
Issue is with the digest appended feature on QAT PMD.
A workaround is also documented.

Signed-off-by: Fiona Trahe 
---
 doc/guides/rel_notes/release_16_11.rst | 13 -
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/doc/guides/rel_notes/release_16_11.rst 
b/doc/guides/rel_notes/release_16_11.rst
index 365b5a3..5f925b5 100644
--- a/doc/guides/rel_notes/release_16_11.rst
+++ b/doc/guides/rel_notes/release_16_11.rst
@@ -213,7 +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.5.0