Lines Matching refs:enqueue

160 core which it was enqueued on. This means that a crypto burst enqueue/dequeue
300 device accepts a burst of Crypto operations using enqueue burst API. On physical
301 Crypto devices the enqueue burst API will place the operations to be processed
303 Crypto operations is usually completed during the enqueue call to the Crypto
308 enqueue call.
389 The burst enqueue API uses a Crypto device identifier and a queue pair
393 The enqueue function returns the number of operations it actually enqueued for
402 The dequeue API uses the same format as the enqueue API of processed but
697 - Flexible enqueue and dequeue operation. The raw data-path APIs gives the
698   user more control to the enqueue and dequeue operations, including the
699   capability of precious enqueue/dequeue count, abandoning enqueue or dequeue
711 set the corresponding enqueue and dequeue function handlers based on the
718 ready for enqueue and dequeue operation. There are two different enqueue
719 functions: ``rte_cryptodev_raw_enqueue`` to enqueue single raw data
720 operation, and ``rte_cryptodev_raw_enqueue_burst`` to enqueue a descriptor
732 functions will return or set the enqueue status. ``rte_cryptodev_raw_enqueue``
736 enqueue status values are:
744 - The negative integer: error occurred during enqueue.
747 set as 0 twice without the enqueue function returning or setting enqueue status
751 for a failed enqueue burst operation and try enqueuing in a whole later.
753 Similar as enqueue, there are two dequeue functions:
782 * CANNOT mix the raw data-path API's enqueue with rte_cryptodev_enqueue_burst,