4 * Copyright(c) 2016-2017 Intel Corporation. All rights reserved.
6 * Redistribution and use in source and binary forms, with or without
7 * modification, are permitted provided that the following conditions
10 * * Redistributions of source code must retain the above copyright
11 * notice, this list of conditions and the following disclaimer.
12 * * Redistributions in binary form must reproduce the above copyright
13 * notice, this list of conditions and the following disclaimer in
14 * the documentation and/or other materials provided with the
16 * * Neither the name of Intel Corporation nor the names of its
17 * contributors may be used to endorse or promote products derived
18 * from this software without specific prior written permission.
20 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
21 * "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
22 * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
23 * A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
24 * OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
25 * SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
26 * LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
27 * DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
28 * THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
29 * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
30 * OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
33 #ifndef _RTE_CRYPTO_SYM_H_
34 #define _RTE_CRYPTO_SYM_H_
37 * @file rte_crypto_sym.h
39 * RTE Definitions for Symmetric Cryptography
41 * Defines symmetric cipher and authentication algorithms and modes, as well
42 * as supported symmetric crypto operation combinations.
52 #include <rte_memory.h>
53 #include <rte_mempool.h>
54 #include <rte_common.h>
57 /** Symmetric Cipher Algorithms */
58 enum rte_crypto_cipher_algorithm {
59 RTE_CRYPTO_CIPHER_NULL = 1,
60 /**< NULL cipher algorithm. No mode applies to the NULL algorithm. */
62 RTE_CRYPTO_CIPHER_3DES_CBC,
63 /**< Triple DES algorithm in CBC mode */
64 RTE_CRYPTO_CIPHER_3DES_CTR,
65 /**< Triple DES algorithm in CTR mode */
66 RTE_CRYPTO_CIPHER_3DES_ECB,
67 /**< Triple DES algorithm in ECB mode */
69 RTE_CRYPTO_CIPHER_AES_CBC,
70 /**< AES algorithm in CBC mode */
71 RTE_CRYPTO_CIPHER_AES_CTR,
72 /**< AES algorithm in Counter mode */
73 RTE_CRYPTO_CIPHER_AES_ECB,
74 /**< AES algorithm in ECB mode */
75 RTE_CRYPTO_CIPHER_AES_F8,
76 /**< AES algorithm in F8 mode */
77 RTE_CRYPTO_CIPHER_AES_XTS,
78 /**< AES algorithm in XTS mode */
80 RTE_CRYPTO_CIPHER_ARC4,
81 /**< (A)RC4 cipher algorithm */
83 RTE_CRYPTO_CIPHER_KASUMI_F8,
84 /**< KASUMI algorithm in F8 mode */
86 RTE_CRYPTO_CIPHER_SNOW3G_UEA2,
87 /**< SNOW 3G algorithm in UEA2 mode */
89 RTE_CRYPTO_CIPHER_ZUC_EEA3,
90 /**< ZUC algorithm in EEA3 mode */
92 RTE_CRYPTO_CIPHER_DES_CBC,
93 /**< DES algorithm in CBC mode */
95 RTE_CRYPTO_CIPHER_AES_DOCSISBPI,
96 /**< AES algorithm using modes required by
97 * DOCSIS Baseline Privacy Plus Spec.
98 * Chained mbufs are not supported in this mode, i.e. rte_mbuf.next
99 * for m_src and m_dst in the rte_crypto_sym_op must be NULL.
102 RTE_CRYPTO_CIPHER_DES_DOCSISBPI,
103 /**< DES algorithm using modes required by
104 * DOCSIS Baseline Privacy Plus Spec.
105 * Chained mbufs are not supported in this mode, i.e. rte_mbuf.next
106 * for m_src and m_dst in the rte_crypto_sym_op must be NULL.
109 RTE_CRYPTO_CIPHER_LIST_END
113 /** Cipher algorithm name strings */
115 rte_crypto_cipher_algorithm_strings[];
117 /** Symmetric Cipher Direction */
118 enum rte_crypto_cipher_operation {
119 RTE_CRYPTO_CIPHER_OP_ENCRYPT,
120 /**< Encrypt cipher operation */
121 RTE_CRYPTO_CIPHER_OP_DECRYPT
122 /**< Decrypt cipher operation */
125 /** Cipher operation name strings */
127 rte_crypto_cipher_operation_strings[];
130 * Symmetric Cipher Setup Data.
132 * This structure contains data relating to Cipher (Encryption and Decryption)
133 * use to create a session.
135 struct rte_crypto_cipher_xform {
136 enum rte_crypto_cipher_operation op;
137 /**< This parameter determines if the cipher operation is an encrypt or
138 * a decrypt operation. For the RC4 algorithm and the F8/CTR modes,
139 * only encrypt operations are valid.
141 enum rte_crypto_cipher_algorithm algo;
142 /**< Cipher algorithm */
145 uint8_t *data; /**< pointer to key data */
146 size_t length; /**< key length in bytes */
150 * For the RTE_CRYPTO_CIPHER_AES_F8 mode of operation, key.data will
151 * point to a concatenation of the AES encryption key followed by a
152 * keymask. As per RFC3711, the keymask should be padded with trailing
153 * bytes to match the length of the encryption key used.
155 * For AES-XTS mode of operation, two keys must be provided and
156 * key.data must point to the two keys concatenated together (Key1 ||
157 * Key2). The cipher key length will contain the total size of both
160 * Cipher key length is in bytes. For AES it can be 128 bits (16 bytes),
161 * 192 bits (24 bytes) or 256 bits (32 bytes).
163 * For the CCM mode of operation, the only supported key length is 128
166 * For the RTE_CRYPTO_CIPHER_AES_F8 mode of operation, key.length
167 * should be set to the combined length of the encryption key and the
168 * keymask. Since the keymask and the encryption key are the same size,
169 * key.length should be set to 2 x the AES encryption key length.
171 * For the AES-XTS mode of operation:
172 * - Two keys must be provided and key.length refers to total length of
174 * - Each key can be either 128 bits (16 bytes) or 256 bits (32 bytes).
175 * - Both keys must have the same size.
179 /**< Starting point for Initialisation Vector or Counter,
180 * specified as number of bytes from start of crypto
181 * operation (rte_crypto_op).
183 * - For block ciphers in CBC or F8 mode, or for KASUMI
184 * in F8 mode, or for SNOW 3G in UEA2 mode, this is the
185 * Initialisation Vector (IV) value.
187 * - For block ciphers in CTR mode, this is the counter.
189 * - For GCM mode, this is either the IV (if the length
190 * is 96 bits) or J0 (for other sizes), where J0 is as
191 * defined by NIST SP800-38D. Regardless of the IV
192 * length, a full 16 bytes needs to be allocated.
194 * - For CCM mode, the first byte is reserved, and the
195 * nonce should be written starting at &iv[1] (to allow
196 * space for the implementation to write in the flags
197 * in the first byte). Note that a full 16 bytes should
198 * be allocated, even though the length field will
199 * have a value less than this.
201 * - For AES-XTS, this is the 128bit tweak, i, from
202 * IEEE Std 1619-2007.
204 * For optimum performance, the data pointed to SHOULD
208 /**< Length of valid IV data.
210 * - For block ciphers in CBC or F8 mode, or for KASUMI
211 * in F8 mode, or for SNOW 3G in UEA2 mode, this is the
212 * length of the IV (which must be the same as the
213 * block length of the cipher).
215 * - For block ciphers in CTR mode, this is the length
216 * of the counter (which must be the same as the block
217 * length of the cipher).
219 * - For GCM mode, this is either 12 (for 96-bit IVs)
220 * or 16, in which case data points to J0.
222 * - For CCM mode, this is the length of the nonce,
223 * which can be in the range 7 to 13 inclusive.
225 } iv; /**< Initialisation vector parameters */
228 /** Symmetric Authentication / Hash Algorithms */
229 enum rte_crypto_auth_algorithm {
230 RTE_CRYPTO_AUTH_NULL = 1,
231 /**< NULL hash algorithm. */
233 RTE_CRYPTO_AUTH_AES_CBC_MAC,
234 /**< AES-CBC-MAC algorithm. Only 128-bit keys are supported. */
235 RTE_CRYPTO_AUTH_AES_CMAC,
236 /**< AES CMAC algorithm. */
237 RTE_CRYPTO_AUTH_AES_GMAC,
238 /**< AES GMAC algorithm. */
239 RTE_CRYPTO_AUTH_AES_XCBC_MAC,
240 /**< AES XCBC algorithm. */
242 RTE_CRYPTO_AUTH_KASUMI_F9,
243 /**< KASUMI algorithm in F9 mode. */
246 /**< MD5 algorithm */
247 RTE_CRYPTO_AUTH_MD5_HMAC,
248 /**< HMAC using MD5 algorithm */
250 RTE_CRYPTO_AUTH_SHA1,
251 /**< 128 bit SHA algorithm. */
252 RTE_CRYPTO_AUTH_SHA1_HMAC,
253 /**< HMAC using 128 bit SHA algorithm. */
254 RTE_CRYPTO_AUTH_SHA224,
255 /**< 224 bit SHA algorithm. */
256 RTE_CRYPTO_AUTH_SHA224_HMAC,
257 /**< HMAC using 224 bit SHA algorithm. */
258 RTE_CRYPTO_AUTH_SHA256,
259 /**< 256 bit SHA algorithm. */
260 RTE_CRYPTO_AUTH_SHA256_HMAC,
261 /**< HMAC using 256 bit SHA algorithm. */
262 RTE_CRYPTO_AUTH_SHA384,
263 /**< 384 bit SHA algorithm. */
264 RTE_CRYPTO_AUTH_SHA384_HMAC,
265 /**< HMAC using 384 bit SHA algorithm. */
266 RTE_CRYPTO_AUTH_SHA512,
267 /**< 512 bit SHA algorithm. */
268 RTE_CRYPTO_AUTH_SHA512_HMAC,
269 /**< HMAC using 512 bit SHA algorithm. */
271 RTE_CRYPTO_AUTH_SNOW3G_UIA2,
272 /**< SNOW 3G algorithm in UIA2 mode. */
274 RTE_CRYPTO_AUTH_ZUC_EIA3,
275 /**< ZUC algorithm in EIA3 mode */
277 RTE_CRYPTO_AUTH_LIST_END
280 /** Authentication algorithm name strings */
282 rte_crypto_auth_algorithm_strings[];
284 /** Symmetric Authentication / Hash Operations */
285 enum rte_crypto_auth_operation {
286 RTE_CRYPTO_AUTH_OP_VERIFY, /**< Verify authentication digest */
287 RTE_CRYPTO_AUTH_OP_GENERATE /**< Generate authentication digest */
290 /** Authentication operation name strings */
292 rte_crypto_auth_operation_strings[];
295 * Authentication / Hash transform data.
297 * This structure contains data relating to an authentication/hash crypto
298 * transforms. The fields op, algo and digest_length are common to all
299 * authentication transforms and MUST be set.
301 struct rte_crypto_auth_xform {
302 enum rte_crypto_auth_operation op;
303 /**< Authentication operation type */
304 enum rte_crypto_auth_algorithm algo;
305 /**< Authentication algorithm selection */
308 uint8_t *data; /**< pointer to key data */
309 size_t length; /**< key length in bytes */
311 /**< Authentication key data.
312 * The authentication key length MUST be less than or equal to the
313 * block size of the algorithm. It is the callers responsibility to
314 * ensure that the key length is compliant with the standard being used
315 * (for example RFC 2104, FIPS 198a).
318 uint16_t digest_length;
319 /**< Length of the digest to be returned. If the verify option is set,
320 * this specifies the length of the digest to be compared for the
323 * It is the caller's responsibility to ensure that the
324 * digest length is compliant with the hash algorithm being used.
325 * If the value is less than the maximum length allowed by the hash,
326 * the result shall be truncated.
331 /**< Starting point for Initialisation Vector or Counter,
332 * specified as number of bytes from start of crypto
333 * operation (rte_crypto_op).
335 * - For KASUMI in F9 mode, SNOW 3G in UIA2 mode,
336 * for ZUC in EIA3 mode and for AES-GMAC, this is the
337 * authentication Initialisation Vector (IV) value.
340 * For optimum performance, the data pointed to SHOULD
344 /**< Length of valid IV data.
346 * - For KASUMI in F9 mode, SNOW3G in UIA2 mode, for
347 * ZUC in EIA3 mode and for AES-GMAC, this is the length
351 } iv; /**< Initialisation vector parameters */
355 /** Symmetric AEAD Algorithms */
356 enum rte_crypto_aead_algorithm {
357 RTE_CRYPTO_AEAD_AES_CCM = 1,
358 /**< AES algorithm in CCM mode. */
359 RTE_CRYPTO_AEAD_AES_GCM,
360 /**< AES algorithm in GCM mode. */
361 RTE_CRYPTO_AEAD_LIST_END
364 /** AEAD algorithm name strings */
366 rte_crypto_aead_algorithm_strings[];
368 /** Symmetric AEAD Operations */
369 enum rte_crypto_aead_operation {
370 RTE_CRYPTO_AEAD_OP_ENCRYPT,
371 /**< Encrypt and generate digest */
372 RTE_CRYPTO_AEAD_OP_DECRYPT
373 /**< Verify digest and decrypt */
376 /** Authentication operation name strings */
378 rte_crypto_aead_operation_strings[];
380 struct rte_crypto_aead_xform {
381 enum rte_crypto_aead_operation op;
382 /**< AEAD operation type */
383 enum rte_crypto_aead_algorithm algo;
384 /**< AEAD algorithm selection */
387 uint8_t *data; /**< pointer to key data */
388 size_t length; /**< key length in bytes */
393 /**< Starting point for Initialisation Vector or Counter,
394 * specified as number of bytes from start of crypto
395 * operation (rte_crypto_op).
397 * - For GCM mode, this is either the IV (if the length
398 * is 96 bits) or J0 (for other sizes), where J0 is as
399 * defined by NIST SP800-38D. Regardless of the IV
400 * length, a full 16 bytes needs to be allocated.
402 * - For CCM mode, the first byte is reserved, and the
403 * nonce should be written starting at &iv[1] (to allow
404 * space for the implementation to write in the flags
405 * in the first byte). Note that a full 16 bytes should
406 * be allocated, even though the length field will
407 * have a value less than this.
409 * For optimum performance, the data pointed to SHOULD
413 /**< Length of valid IV data.
415 * - For GCM mode, this is either 12 (for 96-bit IVs)
416 * or 16, in which case data points to J0.
418 * - For CCM mode, this is the length of the nonce,
419 * which can be in the range 7 to 13 inclusive.
421 } iv; /**< Initialisation vector parameters */
423 uint32_t digest_length;
425 uint16_t add_auth_data_length;
426 /**< The length of the additional authenticated data (AAD) in bytes. */
429 /** Crypto transformation types */
430 enum rte_crypto_sym_xform_type {
431 RTE_CRYPTO_SYM_XFORM_NOT_SPECIFIED = 0, /**< No xform specified */
432 RTE_CRYPTO_SYM_XFORM_AUTH, /**< Authentication xform */
433 RTE_CRYPTO_SYM_XFORM_CIPHER, /**< Cipher xform */
434 RTE_CRYPTO_SYM_XFORM_AEAD /**< AEAD xform */
438 * Symmetric crypto transform structure.
440 * This is used to specify the crypto transforms required, multiple transforms
441 * can be chained together to specify a chain transforms such as authentication
442 * then cipher, or cipher then authentication. Each transform structure can
443 * hold a single transform, the type field is used to specify which transform
444 * is contained within the union
446 struct rte_crypto_sym_xform {
447 struct rte_crypto_sym_xform *next;
448 /**< next xform in chain */
449 enum rte_crypto_sym_xform_type type
453 struct rte_crypto_auth_xform auth;
454 /**< Authentication / hash xform */
455 struct rte_crypto_cipher_xform cipher;
457 struct rte_crypto_aead_xform aead;
462 struct rte_cryptodev_sym_session;
465 * Symmetric Cryptographic Operation.
467 * This structure contains data relating to performing symmetric cryptographic
468 * processing on a referenced mbuf data buffer.
470 * When a symmetric crypto operation is enqueued with the device for processing
471 * it must have a valid *rte_mbuf* structure attached, via m_src parameter,
472 * which contains the source data which the crypto operation is to be performed
474 * While the mbuf is in use by a crypto operation no part of the mbuf should be
475 * changed by the application as the device may read or write to any part of the
476 * mbuf. In the case of hardware crypto devices some or all of the mbuf
477 * may be DMAed in and out of the device, so writing over the original data,
478 * though only the part specified by the rte_crypto_sym_op for transformation
480 * Out-of-place (OOP) operation, where the source mbuf is different to the
481 * destination mbuf, is a special case. Data will be copied from m_src to m_dst.
482 * The part copied includes all the parts of the source mbuf that will be
483 * operated on, based on the cipher.data.offset+cipher.data.length and
484 * auth.data.offset+auth.data.length values in the rte_crypto_sym_op. The part
485 * indicated by the cipher parameters will be transformed, any extra data around
486 * this indicated by the auth parameters will be copied unchanged from source to
488 * Also in OOP operation the cipher.data.offset and auth.data.offset apply to
489 * both source and destination mbufs. As these offsets are relative to the
490 * data_off parameter in each mbuf this can result in the data written to the
491 * destination buffer being at a different alignment, relative to buffer start,
492 * to the data in the source buffer.
494 struct rte_crypto_sym_op {
495 struct rte_mbuf *m_src; /**< source mbuf */
496 struct rte_mbuf *m_dst; /**< destination mbuf */
500 struct rte_cryptodev_sym_session *session;
501 /**< Handle for the initialised session context */
502 struct rte_crypto_sym_xform *xform;
503 /**< Session-less API crypto operation parameters */
510 /**< Starting point for AEAD processing, specified as
511 * number of bytes from start of packet in source
515 /**< The message length, in bytes, of the source buffer
516 * on which the cryptographic operation will be
517 * computed. This must be a multiple of the block size
519 } data; /**< Data offsets and length for AEAD */
522 /**< This points to the location where the digest result
523 * should be inserted (in the case of digest generation)
524 * or where the purported digest exists (in the case of
525 * digest verification).
527 * At session creation time, the client specified the
528 * digest result length with the digest_length member
529 * of the @ref rte_crypto_auth_xform structure. For
530 * physical crypto devices the caller must allocate at
531 * least digest_length of physically contiguous memory
534 * For digest generation, the digest result will
535 * overwrite any data at this location.
538 * For GCM (@ref RTE_CRYPTO_AEAD_AES_GCM), for
539 * "digest result" read "authentication tag T".
541 phys_addr_t phys_addr;
542 /**< Physical address of digest */
543 } digest; /**< Digest parameters */
546 /**< Pointer to Additional Authenticated Data (AAD)
547 * needed for authenticated cipher mechanisms (CCM and
550 * Specifically for CCM (@ref RTE_CRYPTO_AEAD_AES_CCM),
551 * the caller should setup this field as follows:
553 * - the nonce should be written starting at an offset
554 * of one byte into the array, leaving room for the
555 * implementation to write in the flags to the first
558 * - the additional authentication data itself should
559 * be written starting at an offset of 18 bytes into
560 * the array, leaving room for the length encoding in
561 * the first two bytes of the second block.
563 * - the array should be big enough to hold the above
564 * fields, plus any padding to round this up to the
565 * nearest multiple of the block size (16 bytes).
566 * Padding will be added by the implementation.
568 * Finally, for GCM (@ref RTE_CRYPTO_AEAD_AES_GCM), the
569 * caller should setup this field as follows:
571 * - the AAD is written in starting at byte 0
572 * - the array must be big enough to hold the AAD, plus
573 * any space to round this up to the nearest multiple
574 * of the block size (16 bytes).
577 phys_addr_t phys_addr; /**< physical address */
579 /**< Additional authentication parameters */
586 /**< Starting point for cipher processing,
587 * specified as number of bytes from start
588 * of data in the source buffer.
589 * The result of the cipher operation will be
590 * written back into the output buffer
591 * starting at this location.
594 * For SNOW 3G @ RTE_CRYPTO_CIPHER_SNOW3G_UEA2,
595 * KASUMI @ RTE_CRYPTO_CIPHER_KASUMI_F8
596 * and ZUC @ RTE_CRYPTO_CIPHER_ZUC_EEA3,
597 * this field should be in bits.
600 /**< The message length, in bytes, of the
601 * source buffer on which the cryptographic
602 * operation will be computed.
603 * This must be a multiple of the block size
604 * if a block cipher is being used. This is
605 * also the same as the result length.
608 * For SNOW 3G @ RTE_CRYPTO_AUTH_SNOW3G_UEA2,
609 * KASUMI @ RTE_CRYPTO_CIPHER_KASUMI_F8
610 * and ZUC @ RTE_CRYPTO_CIPHER_ZUC_EEA3,
611 * this field should be in bits.
613 } data; /**< Data offsets and length for ciphering */
619 /**< Starting point for hash processing,
620 * specified as number of bytes from start of
621 * packet in source buffer.
624 * For SNOW 3G @ RTE_CRYPTO_AUTH_SNOW3G_UIA2,
625 * KASUMI @ RTE_CRYPTO_AUTH_KASUMI_F9
626 * and ZUC @ RTE_CRYPTO_AUTH_ZUC_EIA3,
627 * this field should be in bits.
630 /**< The message length, in bytes, of the source
631 * buffer that the hash will be computed on.
634 * For SNOW 3G @ RTE_CRYPTO_AUTH_SNOW3G_UIA2,
635 * KASUMI @ RTE_CRYPTO_AUTH_KASUMI_F9
636 * and ZUC @ RTE_CRYPTO_AUTH_ZUC_EIA3,
637 * this field should be in bits.
640 /**< Data offsets and length for authentication */
644 /**< This points to the location where
645 * the digest result should be inserted
646 * (in the case of digest generation)
647 * or where the purported digest exists
648 * (in the case of digest verification).
650 * At session creation time, the client
651 * specified the digest result length with
652 * the digest_length member of the
653 * @ref rte_crypto_auth_xform structure.
654 * For physical crypto devices the caller
655 * must allocate at least digest_length of
656 * physically contiguous memory at this
659 * For digest generation, the digest result
660 * will overwrite any data at this location.
663 phys_addr_t phys_addr;
664 /**< Physical address of digest */
665 } digest; /**< Digest parameters */
673 * Reset the fields of a symmetric operation to their default values.
675 * @param op The crypto operation to be reset.
678 __rte_crypto_sym_op_reset(struct rte_crypto_sym_op *op)
680 memset(op, 0, sizeof(*op));
685 * Allocate space for symmetric crypto xforms in the private data space of the
686 * crypto operation. This also defaults the crypto xform type to
687 * RTE_CRYPTO_SYM_XFORM_NOT_SPECIFIED and configures the chaining of the xforms
688 * in the crypto operation
691 * - On success returns pointer to first crypto xform in crypto operations chain
692 * - On failure returns NULL
694 static inline struct rte_crypto_sym_xform *
695 __rte_crypto_sym_op_sym_xforms_alloc(struct rte_crypto_sym_op *sym_op,
696 void *priv_data, uint8_t nb_xforms)
698 struct rte_crypto_sym_xform *xform;
700 sym_op->xform = xform = (struct rte_crypto_sym_xform *)priv_data;
703 xform->type = RTE_CRYPTO_SYM_XFORM_NOT_SPECIFIED;
704 xform = xform->next = --nb_xforms > 0 ? xform + 1 : NULL;
707 return sym_op->xform;
712 * Attach a session to a symmetric crypto operation
714 * @param sym_op crypto operation
715 * @param sess cryptodev session
718 __rte_crypto_sym_op_attach_sym_session(struct rte_crypto_sym_op *sym_op,
719 struct rte_cryptodev_sym_session *sess)
721 sym_op->session = sess;
731 #endif /* _RTE_CRYPTO_SYM_H_ */