[dpdk-dev,v2] doc: add known issue on QAT PMD into release notes
Checks
Commit Message
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>
---
v2
- fixed trailing whitespace checkpatch errors
doc/guides/rel_notes/release_16_11.rst | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
Comments
On 10/11/16 17:27, Fiona Trahe wrote:
> 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>
> ---
> v2
> - fixed trailing whitespace checkpatch errors
>
Acked-by: John Griffin <john.griffin@intel.com>
> > 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>
Applied, thanks
@@ -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
-----------