This structure contains data relating to performing cryptographic operations. This operation structure is used to contain any operation which is supported by the cryptodev API, PMDs should check the type parameter to verify that the operation is a support function of the device. Crypto operations are enqueued and dequeued in crypto PMDs using the rte_cryptodev_enqueue_burst() / rte_cryptodev_dequeue_burst() .
- examples/ipsec-secgw/esp.c, examples/ipsec-secgw/ipsec.c, examples/l2fwd-crypto/main.c, and examples/vhost_crypto/main.c.
Definition at line 78 of file rte_crypto.h.
operation status - this is reset to RTE_CRYPTO_OP_STATUS_NOT_PROCESSED on allocation from mempool and will be set to RTE_CRYPTO_OP_STATUS_SUCCESS after crypto operation is successfully processed by a crypto PMD
Definition at line 87 of file rte_crypto.h.
Reserved bytes to fill 64 bits for future additions
Definition at line 97 of file rte_crypto.h.
Offset to indicate start of private data (if any). The offset is counted from the start of the rte_crypto_op including IV. The private data may be used by the application to store information which should remain untouched in the library/driver
Definition at line 101 of file rte_crypto.h.
crypto operation mempool which operation is allocated from
Definition at line 110 of file rte_crypto.h.
physical address of crypto operation
Definition at line 114 of file rte_crypto.h.
Asymmetric operation parameters
Definition at line 121 of file rte_crypto.h.
operation specific parameters
The documentation for this struct was generated from the following file: