Lines Matching refs:session
127 /**< The mempool for creating session in sessionless mode */
134 temporary session to process the crypto operations in the session-less mode.
136 PMDs supports session-less mode.
144 Crypto operations, and in the case of symmetric Crypto operations, the session
151 virtual Crypto devices, if the Crypto operation and session and data buffer is
313 For session-based operations, the set and get API provides a mechanism for an
315 with the crypto session.
317 For example, suppose an application is submitting a crypto operation with a session
331 ``user_data_sz`` when creating the session header mempool, otherwise the
333 creating the session header mempool, the get API will always return ``NULL``.
335 For session-less mode, the private user data information can be placed along with the
380 and the session type (session-based/less), a reference to the operation
462 The Crypto device framework provides APIs to create session mempool and allocate
465 create the session header mempool that creates a mempool with proper element
467 session in the mempool's private data field.
469 To create a mempool for storing session private data, the application has two
471 bigger than the maximum session private data size of all crypto devices that
472 will share the same session header. The creation of the mempool shall use the
477 a session header normally takes smaller memory footprint as the session private
480 Once the session mempools have been created, ``rte_cryptodev_sym_session_create()``
481 is used to allocate an uninitialized session from the given mempool.
482 The session then must be initialized using ``rte_cryptodev_sym_session_init()``
487 When a session is no longer used, user must call ``rte_cryptodev_sym_session_clear()``
488 for each of the crypto devices that are using the session, to free all driver
489 private session data. Once this is done, session should be freed using
542 a valid session (or transform chain if in session-less mode) and the minimum
544 specified in the session or the transform
554 struct rte_cryptodev_sym_session *session;
555 /**< Handle for the initialised session context */
665 buffer and attach either the cryptodev sym session, the rte_security session,
666 or the cryptodev xform for session-less operation into the ctx buffer, and
668 algorithm information stored in the session or xform. When the ``is_update``
670 will not initialize the buffer but only update the session or xform and
823 /* Get private session data size. */
827 /* Create session mempool for the session header. */
836 * Create session private data mempool for the
837 * private session data for the crypto device.
848 /* Use of the same mempool for session header and private data */
900 /* Create crypto session and initialize it for the crypto device. */
901 struct rte_cryptodev_sym_session *session;
902 session = rte_cryptodev_sym_session_create(session_pool);
903 if (session == NULL)
906 if (rte_cryptodev_sym_session_init(cdev_id, session,
943 /* Attach the crypto session to the operation */
944 rte_crypto_op_attach_sym_session(op, session);
993 It is the application's responsibility to create and manage the session mempools.
998 get the private size of asymmetric session on a given crypto device. This
1000 session size of all crypto devices to create a single session mempool.
1001 If instead an application creates multiple asymmetric session mempools,
1003 the size of an uninitialized session.
1005 Once the session mempools have been created, ``rte_cryptodev_asym_session_create()``
1006 is used to allocate an uninitialized asymmetric session from the given mempool.
1007 The session then must be initialized using ``rte_cryptodev_asym_session_init()``
1012 When a session is no longer used, user must call ``rte_cryptodev_asym_session_clear()``
1013 for each of the crypto devices that are using the session, to free all driver
1014 private asymmetric session data. Once this is done, session should be freed using
1020 Asymmetric crypto framework supports session-less operations as well.
1059 RSA, Modular, Diffie-Hellman or DSA operations depending upon session it is attached
1062 Every operation must carry a valid session handle which further carries information
1065 on xform information within session, PMD picks up and process respective op_param
1121 /* Get private asym session data size. */
1125 * Create session mempool, with two objects per session,
1126 * one for the session header and another one for the
1127 * private asym session data for the crypto device.
1183 /* Create asym crypto session and initialize it for the crypto device. */
1210 /* Attach the asym crypto session to the operation */