d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

doc: add known issue with QAT

Browse Source 
Issue is with the digest appended feature on QAT PMD.
A workaround is also documented.

Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
Acked-by: John Griffin <john.griffin@intel.com>
This commit is contained in:
Fiona Trahe 2016-11-10 17:27:21 +00:00 committed by Thomas Monjalon
parent dd030a0ee8
commit fd8036ef74
1 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/guides/rel_notes/release_16_11.rst
View File

@ -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
-----------