DPDK
21.02.0

#include <rte_crypto_sym.h>
Data Fields  
enum rte_crypto_cipher_operation  op 
enum rte_crypto_cipher_algorithm  algo 
struct {  
const uint8_t * data  
uint16_t length  
}  key 
struct {  
uint16_t offset  
uint16_t length  
}  iv 
Symmetric Cipher Setup Data.
This structure contains data relating to Cipher (Encryption and Decryption) use to create a session.
Definition at line 189 of file rte_crypto_sym.h.
enum rte_crypto_cipher_operation op 
This parameter determines if the cipher operation is an encrypt or a decrypt operation. For the RC4 algorithm and the F8/CTR modes, only encrypt operations are valid.
Definition at line 190 of file rte_crypto_sym.h.
enum rte_crypto_cipher_algorithm algo 
Cipher algorithm
Definition at line 195 of file rte_crypto_sym.h.
const uint8_t* data 
pointer to key data
Definition at line 199 of file rte_crypto_sym.h.
uint16_t length 
key length in bytes
Length of valid IV data.
Definition at line 200 of file rte_crypto_sym.h.
struct { ... } key 
Cipher key
For the RTE_CRYPTO_CIPHER_AES_F8 mode of operation, key.data will point to a concatenation of the AES encryption key followed by a keymask. As per RFC3711, the keymask should be padded with trailing bytes to match the length of the encryption key used.
Cipher key length is in bytes. For AES it can be 128 bits (16 bytes), 192 bits (24 bytes) or 256 bits (32 bytes).
For the RTE_CRYPTO_CIPHER_AES_F8 mode of operation, key.length should be set to the combined length of the encryption key and the keymask. Since the keymask and the encryption key are the same size, key.length should be set to 2 x the AES encryption key length.
For the AESXTS mode of operation:
uint16_t offset 
Starting point for Initialisation Vector or Counter, specified as number of bytes from start of crypto operation (rte_crypto_op).
For optimum performance, the data pointed to SHOULD be 8byte aligned.
Definition at line 226 of file rte_crypto_sym.h.
struct { ... } iv 
Initialisation vector parameters