[PATCH 22/40] cryptodev: move RSA padding into separate struct

[Arek Kusztal]

- move RSA padding into separate struct.
More padding members should be added into padding,
therefore having separate struct for padding parameters will
make this more readable.

Signed-off-by: Arek Kusztal <arkadiuszx.kusz...@intel.com>
---
 lib/cryptodev/rte_crypto_asym.h | 42 +++++++++++++++++++++++------------------
 1 file changed, 24 insertions(+), 18 deletions(-)

diff --git a/lib/cryptodev/rte_crypto_asym.h b/lib/cryptodev/rte_crypto_asym.h
index 73ff9ff815..97c3fbee38 100644
--- a/lib/cryptodev/rte_crypto_asym.h
+++ b/lib/cryptodev/rte_crypto_asym.h
@@ -201,6 +201,28 @@ struct rte_crypto_rsa_priv_key_qt {
 };
 
 /**
+ * RSA padding type
+ */
+struct rte_crypto_rsa_padding {
+       enum rte_crypto_rsa_padding_type type;
+       /**< RSA padding scheme to be used for transform */
+       enum rte_crypto_auth_algorithm md;
+       /**< Hash algorithm to be used for data hash if padding
+        * scheme is either OAEP or PSS. Valid hash algorithms
+        * are:
+        * MD5, SHA1, SHA224, SHA256, SHA384, SHA512
+        */
+       enum rte_crypto_auth_algorithm mgf1md;
+       /**<
+        * Hash algorithm to be used for mask generation if
+        * padding scheme is either OAEP or PSS. If padding
+        * scheme is unspecified data hash algorithm is used
+        * for mask generation. Valid hash algorithms are:
+        * MD5, SHA1, SHA224, SHA256, SHA384, SHA512
+        */
+};
+
+/**
  * Asymmetric RSA transform data
  *
  * Structure describing RSA xform params
@@ -355,25 +377,9 @@ struct rte_crypto_rsa_op_param {
         *
         * All data is in Octet-string network byte order format.
         */
+       struct rte_crypto_rsa_padding padding;
+       /**< RSA padding information */
 
-       enum rte_crypto_rsa_padding_type pad;
-       /**< RSA padding scheme to be used for transform */
-
-       enum rte_crypto_auth_algorithm md;
-       /**< Hash algorithm to be used for data hash if padding
-        * scheme is either OAEP or PSS. Valid hash algorithms
-        * are:
-        * MD5, SHA1, SHA224, SHA256, SHA384, SHA512
-        */
-
-       enum rte_crypto_auth_algorithm mgf1md;
-       /**<
-        * Hash algorithm to be used for mask generation if
-        * padding scheme is either OAEP or PSS. If padding
-        * scheme is unspecified data hash algorithm is used
-        * for mask generation. Valid hash algorithms are:
-        * MD5, SHA1, SHA224, SHA256, SHA384, SHA512
-        */
 };
 
 /**
-- 
2.13.6