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.
329 uint16_t add_auth_data_length;
330 /**< The length of the additional authenticated data (AAD) in bytes.
331 * The maximum permitted value is 65535 (2^16 - 1) bytes, unless
332 * otherwise specified below.
338 /**< Starting point for Initialisation Vector or Counter,
339 * specified as number of bytes from start of crypto
340 * operation (rte_crypto_op).
342 * - For KASUMI in F9 mode, SNOW 3G in UIA2 mode,
343 * for ZUC in EIA3 mode and for AES-GMAC, this is the
344 * authentication Initialisation Vector (IV) value.
347 * For optimum performance, the data pointed to SHOULD
351 /**< Length of valid IV data.
353 * - For KASUMI in F9 mode, SNOW3G in UIA2 mode, for
354 * ZUC in EIA3 mode and for AES-GMAC, this is the length
358 } iv; /**< Initialisation vector parameters */
362 /** Symmetric AEAD Algorithms */
363 enum rte_crypto_aead_algorithm {
364 RTE_CRYPTO_AEAD_AES_CCM = 1,
365 /**< AES algorithm in CCM mode. */
366 RTE_CRYPTO_AEAD_AES_GCM,
367 /**< AES algorithm in GCM mode. */
368 RTE_CRYPTO_AEAD_LIST_END
371 /** AEAD algorithm name strings */
373 rte_crypto_aead_algorithm_strings[];
375 /** Symmetric AEAD Operations */
376 enum rte_crypto_aead_operation {
377 RTE_CRYPTO_AEAD_OP_ENCRYPT,
378 /**< Encrypt and generate digest */
379 RTE_CRYPTO_AEAD_OP_DECRYPT
380 /**< Verify digest and decrypt */
383 /** Authentication operation name strings */
385 rte_crypto_aead_operation_strings[];
387 struct rte_crypto_aead_xform {
388 enum rte_crypto_aead_operation op;
389 /**< AEAD operation type */
390 enum rte_crypto_aead_algorithm algo;
391 /**< AEAD algorithm selection */
394 uint8_t *data; /**< pointer to key data */
395 size_t length; /**< key length in bytes */
400 /**< Starting point for Initialisation Vector or Counter,
401 * specified as number of bytes from start of crypto
402 * operation (rte_crypto_op).
404 * - For GCM mode, this is either the IV (if the length
405 * is 96 bits) or J0 (for other sizes), where J0 is as
406 * defined by NIST SP800-38D. Regardless of the IV
407 * length, a full 16 bytes needs to be allocated.
409 * - For CCM mode, the first byte is reserved, and the
410 * nonce should be written starting at &iv[1] (to allow
411 * space for the implementation to write in the flags
412 * in the first byte). Note that a full 16 bytes should
413 * be allocated, even though the length field will
414 * have a value less than this.
416 * For optimum performance, the data pointed to SHOULD
420 /**< Length of valid IV data.
422 * - For GCM mode, this is either 12 (for 96-bit IVs)
423 * or 16, in which case data points to J0.
425 * - For CCM mode, this is the length of the nonce,
426 * which can be in the range 7 to 13 inclusive.
428 } iv; /**< Initialisation vector parameters */
430 uint32_t digest_length;
432 uint16_t add_auth_data_length;
433 /**< The length of the additional authenticated data (AAD) in bytes. */
436 /** Crypto transformation types */
437 enum rte_crypto_sym_xform_type {
438 RTE_CRYPTO_SYM_XFORM_NOT_SPECIFIED = 0, /**< No xform specified */
439 RTE_CRYPTO_SYM_XFORM_AUTH, /**< Authentication xform */
440 RTE_CRYPTO_SYM_XFORM_CIPHER, /**< Cipher xform */
441 RTE_CRYPTO_SYM_XFORM_AEAD /**< AEAD xform */
445 * Symmetric crypto transform structure.
447 * This is used to specify the crypto transforms required, multiple transforms
448 * can be chained together to specify a chain transforms such as authentication
449 * then cipher, or cipher then authentication. Each transform structure can
450 * hold a single transform, the type field is used to specify which transform
451 * is contained within the union
453 struct rte_crypto_sym_xform {
454 struct rte_crypto_sym_xform *next;
455 /**< next xform in chain */
456 enum rte_crypto_sym_xform_type type
460 struct rte_crypto_auth_xform auth;
461 /**< Authentication / hash xform */
462 struct rte_crypto_cipher_xform cipher;
464 struct rte_crypto_aead_xform aead;
469 struct rte_cryptodev_sym_session;
472 * Symmetric Cryptographic Operation.
474 * This structure contains data relating to performing symmetric cryptographic
475 * processing on a referenced mbuf data buffer.
477 * When a symmetric crypto operation is enqueued with the device for processing
478 * it must have a valid *rte_mbuf* structure attached, via m_src parameter,
479 * which contains the source data which the crypto operation is to be performed
481 * While the mbuf is in use by a crypto operation no part of the mbuf should be
482 * changed by the application as the device may read or write to any part of the
483 * mbuf. In the case of hardware crypto devices some or all of the mbuf
484 * may be DMAed in and out of the device, so writing over the original data,
485 * though only the part specified by the rte_crypto_sym_op for transformation
487 * Out-of-place (OOP) operation, where the source mbuf is different to the
488 * destination mbuf, is a special case. Data will be copied from m_src to m_dst.
489 * The part copied includes all the parts of the source mbuf that will be
490 * operated on, based on the cipher.data.offset+cipher.data.length and
491 * auth.data.offset+auth.data.length values in the rte_crypto_sym_op. The part
492 * indicated by the cipher parameters will be transformed, any extra data around
493 * this indicated by the auth parameters will be copied unchanged from source to
495 * Also in OOP operation the cipher.data.offset and auth.data.offset apply to
496 * both source and destination mbufs. As these offsets are relative to the
497 * data_off parameter in each mbuf this can result in the data written to the
498 * destination buffer being at a different alignment, relative to buffer start,
499 * to the data in the source buffer.
501 struct rte_crypto_sym_op {
502 struct rte_mbuf *m_src; /**< source mbuf */
503 struct rte_mbuf *m_dst; /**< destination mbuf */
507 struct rte_cryptodev_sym_session *session;
508 /**< Handle for the initialised session context */
509 struct rte_crypto_sym_xform *xform;
510 /**< Session-less API crypto operation parameters */
517 /**< Starting point for AEAD processing, specified as
518 * number of bytes from start of packet in source
522 /**< The message length, in bytes, of the source buffer
523 * on which the cryptographic operation will be
524 * computed. This must be a multiple of the block size
526 } data; /**< Data offsets and length for AEAD */
529 /**< This points to the location where the digest result
530 * should be inserted (in the case of digest generation)
531 * or where the purported digest exists (in the case of
532 * digest verification).
534 * At session creation time, the client specified the
535 * digest result length with the digest_length member
536 * of the @ref rte_crypto_auth_xform structure. For
537 * physical crypto devices the caller must allocate at
538 * least digest_length of physically contiguous memory
541 * For digest generation, the digest result will
542 * overwrite any data at this location.
545 * For GCM (@ref RTE_CRYPTO_AEAD_AES_GCM), for
546 * "digest result" read "authentication tag T".
548 phys_addr_t phys_addr;
549 /**< Physical address of digest */
550 } digest; /**< Digest parameters */
553 /**< Pointer to Additional Authenticated Data (AAD)
554 * needed for authenticated cipher mechanisms (CCM and
557 * Specifically for CCM (@ref RTE_CRYPTO_AEAD_AES_CCM),
558 * the caller should setup this field as follows:
560 * - the nonce should be written starting at an offset
561 * of one byte into the array, leaving room for the
562 * implementation to write in the flags to the first
565 * - the additional authentication data itself should
566 * be written starting at an offset of 18 bytes into
567 * the array, leaving room for the length encoding in
568 * the first two bytes of the second block.
570 * - the array should be big enough to hold the above
571 * fields, plus any padding to round this up to the
572 * nearest multiple of the block size (16 bytes).
573 * Padding will be added by the implementation.
575 * Finally, for GCM (@ref RTE_CRYPTO_AEAD_AES_GCM), the
576 * caller should setup this field as follows:
578 * - the AAD is written in starting at byte 0
579 * - the array must be big enough to hold the AAD, plus
580 * any space to round this up to the nearest multiple
581 * of the block size (16 bytes).
584 phys_addr_t phys_addr; /**< physical address */
586 /**< Additional authentication parameters */
593 /**< Starting point for cipher processing,
594 * specified as number of bytes from start
595 * of data in the source buffer.
596 * The result of the cipher operation will be
597 * written back into the output buffer
598 * starting at this location.
601 * For SNOW 3G @ RTE_CRYPTO_CIPHER_SNOW3G_UEA2,
602 * KASUMI @ RTE_CRYPTO_CIPHER_KASUMI_F8
603 * and ZUC @ RTE_CRYPTO_CIPHER_ZUC_EEA3,
604 * this field should be in bits.
607 /**< The message length, in bytes, of the
608 * source buffer on which the cryptographic
609 * operation will be computed.
610 * This must be a multiple of the block size
611 * if a block cipher is being used. This is
612 * also the same as the result length.
615 * For SNOW 3G @ RTE_CRYPTO_AUTH_SNOW3G_UEA2,
616 * KASUMI @ RTE_CRYPTO_CIPHER_KASUMI_F8
617 * and ZUC @ RTE_CRYPTO_CIPHER_ZUC_EEA3,
618 * this field should be in bits.
620 } data; /**< Data offsets and length for ciphering */
626 /**< Starting point for hash processing,
627 * specified as number of bytes from start of
628 * packet in source buffer.
631 * For SNOW 3G @ RTE_CRYPTO_AUTH_SNOW3G_UIA2,
632 * KASUMI @ RTE_CRYPTO_AUTH_KASUMI_F9
633 * and ZUC @ RTE_CRYPTO_AUTH_ZUC_EIA3,
634 * this field should be in bits.
637 /**< The message length, in bytes, of the source
638 * buffer that the hash will be computed on.
641 * For SNOW 3G @ RTE_CRYPTO_AUTH_SNOW3G_UIA2,
642 * KASUMI @ RTE_CRYPTO_AUTH_KASUMI_F9
643 * and ZUC @ RTE_CRYPTO_AUTH_ZUC_EIA3,
644 * this field should be in bits.
647 /**< Data offsets and length for authentication */
651 /**< This points to the location where
652 * the digest result should be inserted
653 * (in the case of digest generation)
654 * or where the purported digest exists
655 * (in the case of digest verification).
657 * At session creation time, the client
658 * specified the digest result length with
659 * the digest_length member of the
660 * @ref rte_crypto_auth_xform structure.
661 * For physical crypto devices the caller
662 * must allocate at least digest_length of
663 * physically contiguous memory at this
666 * For digest generation, the digest result
667 * will overwrite any data at this location.
670 phys_addr_t phys_addr;
671 /**< Physical address of digest */
672 } digest; /**< Digest parameters */
676 /**< Pointer to Additional Authenticated
677 * Data (AAD) needed for authenticated cipher
678 * mechanisms (CCM and GCM).
680 * The length of the data pointed to by this
681 * field is set up for the session in the @ref
682 * rte_crypto_auth_xform structure as part of
683 * the @ref rte_cryptodev_sym_session_create
685 * This length must not exceed 65535 (2^16-1)
689 phys_addr_t phys_addr; /**< physical address */
691 /**< Additional authentication parameters */
699 * Reset the fields of a symmetric operation to their default values.
701 * @param op The crypto operation to be reset.
704 __rte_crypto_sym_op_reset(struct rte_crypto_sym_op *op)
706 memset(op, 0, sizeof(*op));
711 * Allocate space for symmetric crypto xforms in the private data space of the
712 * crypto operation. This also defaults the crypto xform type to
713 * RTE_CRYPTO_SYM_XFORM_NOT_SPECIFIED and configures the chaining of the xforms
714 * in the crypto operation
717 * - On success returns pointer to first crypto xform in crypto operations chain
718 * - On failure returns NULL
720 static inline struct rte_crypto_sym_xform *
721 __rte_crypto_sym_op_sym_xforms_alloc(struct rte_crypto_sym_op *sym_op,
722 void *priv_data, uint8_t nb_xforms)
724 struct rte_crypto_sym_xform *xform;
726 sym_op->xform = xform = (struct rte_crypto_sym_xform *)priv_data;
729 xform->type = RTE_CRYPTO_SYM_XFORM_NOT_SPECIFIED;
730 xform = xform->next = --nb_xforms > 0 ? xform + 1 : NULL;
733 return sym_op->xform;
738 * Attach a session to a symmetric crypto operation
740 * @param sym_op crypto operation
741 * @param sess cryptodev session
744 __rte_crypto_sym_op_attach_sym_session(struct rte_crypto_sym_op *sym_op,
745 struct rte_cryptodev_sym_session *sess)
747 sym_op->session = sess;
757 #endif /* _RTE_CRYPTO_SYM_H_ */