GBalakrishna replied on github web page:
include/odp/api/spec/crypto.h
line 35
@@ -381,8 +394,15 @@ typedef struct odp_crypto_op_param_t {
/** Pointer to ADD */
uint8_t *ptr;
- /** AAD length in bytes. Use odp_crypto_auth_capability() for
- * supported AAD lengths. */
+ /** AAD length in bytes.
+ *
+ * Used only when AAD length is variable within the session.
+ * When AAD length is constant, this must be set to zero and
+ * session level AAD length parameter is used instead.
+ *
+ * Use odp_crypto_auth_capability() for supported AAD lengths.
+ * The default value is zero.
+ */
uint32_t length;
Comment:
@psavol in dpdk 17.08 there is no support of variable aad length but only
session specific aad length. ex: If application tries to set variable length
instead of constant length, dpdk crypto operation will fail. Because once the
crypto session is created with auth_aad_len=0, dpdk driver will use zero length
in encryption_gcm & decryption_gcm.
> Bill Fischofer(Bill-Fischofer-Linaro) wrote:
> Why this restriction? Wouldn't it be cleaner to say this is simply a
> session-level default and if individual ops have a non-zero AAD they serve as
> overrides?
https://github.com/Linaro/odp/pull/279#discussion_r149787708
updated_at 2017-11-08 20:28:52
