numam-dpdk/drivers/crypto/qat
Thomas Monjalon f5862ae99e cryptodev: revert Chacha20-Poly1305 AEAD algorithm
API makes think that rte_cryptodev_info_get() cannot return
a value >= 3 (RTE_CRYPTO_AEAD_LIST_END in 19.11).
20.02-rc1 was returning 3 (RTE_CRYPTO_AEAD_CHACHA20_POLY1305).
So the ABI compatibility contract was broken.

It could be solved with some function versioning,
but because a lack of time, the feature is reverted for now.

This reverts following commits:
- 6c9f3b347e ("cryptodev: add Chacha20-Poly1305 AEAD algorithm")
- 2c512e64d6 ("crypto/qat: support Chacha Poly")
- d55e01f579 ("test/crypto: add Chacha Poly cases")

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2020-02-05 15:14:46 +01:00
..
meson.build drivers: add reasons for components being disabled 2019-07-02 23:21:11 +02:00
qat_asym_capabilities.h crypto/qat: support RSA in asym 2019-10-23 16:57:06 +02:00
qat_asym_pmd.c crypto/qat: add minimum enqueue threshold 2020-01-15 16:45:04 +01:00
qat_asym_pmd.h crypto/qat: add minimum enqueue threshold 2020-01-15 16:45:04 +01:00
qat_asym.c crypto/qat: support RSA CRT in asym 2019-10-23 16:57:06 +02:00
qat_asym.h crypto/qat: support RSA CRT in asym 2019-10-23 16:57:06 +02:00
qat_sym_capabilities.h cryptodev: revert Chacha20-Poly1305 AEAD algorithm 2020-02-05 15:14:46 +01:00
qat_sym_pmd.c cryptodev: revert Chacha20-Poly1305 AEAD algorithm 2020-02-05 15:14:46 +01:00
qat_sym_pmd.h crypto/qat: add minimum enqueue threshold 2020-01-15 16:45:04 +01:00
qat_sym_session.c cryptodev: revert Chacha20-Poly1305 AEAD algorithm 2020-02-05 15:14:46 +01:00
qat_sym_session.h crypto/qat: handle Single Pass Crypto Requests on GEN3 2019-10-09 11:50:12 +02:00
qat_sym.c crypto/qat: fix null auth when using VFIO 2019-10-23 16:57:06 +02:00
qat_sym.h common/qat: add scatter-gather header 2018-07-25 08:19:54 +02:00
README crypto/qat: move common qat files to common dir 2018-07-11 00:55:30 +02:00

# SPDX-License-Identifier: BSD-3-Clause
# Copyright(c) 2015-2018 Intel Corporation

Makefile for crypto QAT PMD is in common/qat directory.
The build for the QAT driver is done from there as only one library is built for the
whole QAT pci device and that library includes all the services (crypto, compression)
which are enabled on the device.