- removed asymnetric crypto xform next field.
Rationale behind having chaining in symmetric crypto
was a fact that encryption and authentication are usually
done on the same set of data independent of algorithm.
HW usually will be able to handle it in one PCI call.
In asymmetric there is no such relation between algorithms,
therefore next field would be useless.
Signed-off-by: Arek Kusztal <arkadiuszx.kusz...@intel.com>
---
lib/cryptodev/rte_crypto_asym.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/lib/cryptodev/rte_crypto_asym.h b/lib/cryptodev/rte_crypto_asym.h
index 1652a434a5..b355cbe5fa 100644
--- a/lib/cryptodev/rte_crypto_asym.h
+++ b/lib/cryptodev/rte_crypto_asym.h
@@ -492,8 +492,6 @@ struct rte_crypto_ecpm_op_param {
* Structure describing asym xforms.
*/
struct rte_crypto_asym_xform {
- struct rte_crypto_asym_xform *next;
- /**< Pointer to next xform to set up xform chain.*/
enum rte_crypto_asym_xform_type xform_type;
/**< Asymmetric crypto transform */
--
2.13.6
