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.
345 The burst enqueue API uses a Crypto device identifier and a queue pair
349 The enqueue function returns the number of operations it actually enqueued for
358 The dequeue API uses the same format as the enqueue API of processed but
653 - Flexible enqueue and dequeue operation. The raw data-path APIs gives the
654   user more control to the enqueue and dequeue operations, including the
655   capability of precious enqueue/dequeue count, abandoning enqueue or dequeue
667 set the corresponding enqueue and dequeue function handlers based on the
674 ready for enqueue and dequeue operation. There are two different enqueue
675 functions: ``rte_cryptodev_raw_enqueue`` to enqueue single raw data
676 operation, and ``rte_cryptodev_raw_enqueue_burst`` to enqueue a descriptor
688 functions will return or set the enqueue status. ``rte_cryptodev_raw_enqueue``
692 enqueue status values are:
700 - The negative integer: error occurred during enqueue.
703 set as 0 twice without the enqueue function returning or setting enqueue status
707 for a failed enqueue burst operation and try enqueuing in a whole later.
709 Similar as enqueue, there are two dequeue functions:
738 * CANNOT mix the raw data-path API's enqueue with rte_cryptodev_enqueue_burst,