Home
last modified time | relevance | path

Searched refs:operation (Results 1 – 25 of 149) sorted by relevance

123456

/dpdk/doc/guides/sample_app_ug/
H A Dl2_forward_crypto.rst17 with a crypto device capable of doing that operation,
204 Crypto operation specification
212 If no parameter is passed, the default crypto operation is:
247 check which ones are capable of performing the operation.
291 Crypto operation creation
300 :end-before: >8 End of crypto operation allocated and filled.
303 After filling the crypto operation (including session attachment),
309 after the operation is done (in-place).
311 Crypto operation enqueuing/dequeuing
317 which will perform the operation at that moment:
[all …]
H A Dbbdev_app.rst16 The Baseband device sample application performs a loop-back operation using a
19 operation -> dequeued from the downlink baseband device -> enqueued for uplink
20 baseband operation -> dequeued from the baseband device -> then the received
59 the specified baseband operation are available on application initialization.
/dpdk/doc/guides/prog_guide/
H A Dcryptodev_lib.rst177 (AEAD) operation.
199 supports are defined by the operation type, the operation transform, the
423 The operation structure includes the operation type, the operation status
431 operation for applications purposes.
435 to process the requested operation.
572 driver which is processing the operation.
653 dequeuing an operation before. This mode of operation allows cryptodevs which
658 To perform a synchronous operation a call to
670 for each operation.
738 - ``1``: the operation(s) is/are enqueued successfully.
[all …]
H A Dcompressdev.rst148 to another compression operation.
159 output data. The operation structure includes the operation type (stateless or stateful),
169 by the compression PMD to process the requested operation.
183 compression operations from a given compression operation mempool.
184 The operation gets reset before being returned to a user so that operation
289 Compression API Stateless operation
303 priv_xform in Stateless operation
409 wants the operation to be completed.
421 Compression API Stateful operation
439 operation with flush value = RTE_COMP_FLUSH_FULL/FINAL is complete.
[all …]
H A Dbbdev.rst355 The operation structure by itself defines the operation type. It includes an
356 operation status, a reference to the operation specific data, which can vary in
366 to process the requested operation.
396 operation to its allocating pool.
453 operation.
502 undergoing the operation.
504 the operation.
716 The operation flags that can be set for each LDPC encode operation are
835 The valid modes of operation are:
875 The operation flags that can be set for each LDPC decode operation are
[all …]
H A Dstack_lib.rst48 and one thread being preempted/delayed in a push or pop operation will not
51 The lock-free push operation enqueues a linked list of pointers by pointing the
53 pointer to the head of the list. The operation retries if it is unsuccessful
57 The lock-free pop operation first reserves one or more list elements by
58 adjusting the stack length, to ensure the dequeue operation will succeed
H A Dring_lib.rst144 The enqueue operation is finished.
197 The dequeue operation is finished.
239 the CAS operation fails, and the code restarts at first step.
242 the CAS operation is successful, and processing continues.
257 The CAS operation is retried on core 2 with success.
274 This is only true on core 1. The operation is finished on core 1.
288 The operation is also finished on core 2.
405 In that mode enqueue/dequeue operation is fully serialized:
406 at any given moment only one enqueue/dequeue operation can proceed.
453 with enqueue(/dequeue) operation till ``_finish_`` completes.
[all …]
H A Dpacket_distrib_lib.rst8 while supporting single packet at a time operation.
12 The model of operation is shown in the diagram below.
16 Packet Distributor mode of operation
18 There are two modes of operation of the API in the distributor library,
27 The operation of the distributor is as follows:
H A Ddmadev.rst30 * The DMA operation request must be submitted to the virtual DMA channel.
78 returned. This ``ring_idx`` can be used by applications to track per operation
106 completed operations along with the status of each operation (filled into the
108 completed operation's ``ring_idx`` which could help user track operations within
H A Dpacket_framework.rst37 As result of lookup operation for the current packet in the current table,
111 defines the initialization and run-time operation of the port.
214 and run-time operation of the table.
309 The performance of the hash table lookup operation is greatly improved,
425 otherwise the key add operation fails.
451 The key lookup operation is split between two CPU cores.
455 and performs the bucket search step of the key lookup operation.
459 and also performs the bucket search step of the key lookup operation.
705 This does not impact the performance of the key lookup operation,
946 This does not impact the performance of the key lookup operation,
[all …]
H A Devent_crypto_adapter.rst22 The application can choose to submit a crypto operation directly to
46 which is needed to enqueue an event after the crypto operation is completed.
66 submits the crypto operations to the cryptodev. After the crypto operation is
71 to enqueue a crypto operation in addition to the event information (response
72 information) needed to enqueue an event after the crypto operation has
230 an event after the crypto operation has completed. The request and response
/dpdk/doc/guides/dmadevs/
H A Dioat.rst93 documentation for details on operation enqueue, submission and completion API usage.
99 occurs with an operation. If an error was encountered, ``rte_dma_completed_status()`` must be used
101 of each individual operation which is filled in to the ``status`` array provided as parameter
106 * ``RTE_DMA_STATUS_SUCCESSFUL``: The operation was successful.
107 * ``RTE_DMA_STATUS_INVALID_SRC_ADDR``: The operation failed due to an invalid source address.
108 * ``RTE_DMA_STATUS_INVALID_DST_ADDR``: The operation failed due to an invalid destination address.
109 * ``RTE_DMA_STATUS_INVALID_LENGTH``: The operation failed due to an invalid descriptor length.
111 * ``RTE_DMA_STATUS_ERROR_UNKNOWN``: The operation failed due to an unspecified error.
115 which operation failed and reset the device to continue processing operations:
H A Didxd.rst181 documentation for details on operation enqueue, submission and completion API usage.
187 occurs in an operation. If an error was encountered, ``rte_dma_completed_status()`` must be used
194 * ``RTE_DMA_STATUS_SUCCESSFUL``: The operation was successful.
195 * ``RTE_DMA_STATUS_INVALID_OPCODE``: The operation failed due to an invalid operation code.
196 * ``RTE_DMA_STATUS_INVALID_LENGTH``: The operation failed due to an invalid data length.
197 * ``RTE_DMA_STATUS_NOT_ATTEMPTED``: The operation was not attempted.
198 * ``RTE_DMA_STATUS_ERROR_UNKNOWN``: The operation failed due to an unspecified error.
202 which operation failed and kick off the device to continue processing operations:
/dpdk/lib/pdump/
H A Drte_pdump.c182 if (operation == ENABLE) { in pdump_register_rx_callbacks()
203 } else if (operation == DISABLE) { in pdump_register_rx_callbacks()
240 if (operation == ENABLE) { in pdump_register_tx_callbacks()
261 } else if (operation == DISABLE) { in pdump_register_tx_callbacks()
292 uint16_t operation; in set_pdump_rxtx_cbs() local
320 operation = p->op; in set_pdump_rxtx_cbs()
370 operation, p->snaplen); in set_pdump_rxtx_cbs()
380 operation, p->snaplen); in set_pdump_rxtx_cbs()
526 uint16_t operation, in pdump_prepare_client_request() argument
542 req->op = operation; in pdump_prepare_client_request()
[all …]
/dpdk/doc/guides/tools/
H A Dtestbbdev.rst102 - Performs full operation of enqueue and dequeue
113 the point the operation is put on the accelerator queue.
118 time (us) consumed to dequeue one operation.
129 - Performs full operation of enqueue and dequeue
137 - Performs full operation of enqueue and dequeue
225 The prefix trivially defines which type of operation is included :
472 Chain of operation statuses that are expected after operation is performed.
555 Chain of operation statuses that are expected after operation is performed.
676 Chain of operation statuses that are expected after operation is performed.
778 Chain of flags for LDPC encoder operation based on the
[all …]
H A Dcomp_perf.rst20 the number of cycles per operation for the 3 phases: setup, enqueue_burst and
37 * Stateful operation is not supported in this version.
77 ``--burst-sz N``: compress operation burst size
85 …``--operation [comp/decomp/comp_and_decomp]``: perform test on compression, decompression or both …
H A Dcryptoperf.rst12 execution. Cipher parameters, type of device, type of operation and
37 It is possible linearized input segmented packets just before crypto operation
168 Set operation type, where ``name`` is one of the following::
217 Set cipher operation mode, where ``mode`` is one of the following::
258 Set authentication operation mode, where ``mode`` is one of
282 Set AEAD operation mode, where ``mode`` is one of
377 Key used in cipher operation.
381 Key used in auth operation.
/dpdk/doc/guides/cryptodevs/
H A Doverview.rst18 being the operation in-place (input address = output address).
37 which means that Out-of-place operation is supported,
41 operation (Sign and Decrypt) using exponent key type only.
44 operation (Sign and Decrypt) using quintuple (crt) type key only.
H A Dscheduler.rst30 * Sessionless crypto operation is not supported
31 * OOP crypto operation is not supported when the crypto op reordering feature
99 operation:
116 operations to them based on their data lengths. A crypto operation will be
145 crypto operation burst to the primary worker. When one or more crypto
H A Dnull.rst10 operation is to operate and it only has support for a single cipher and
15 a dequeue call as long as the mbuf has a valid rte_mbuf_offload operation with
/dpdk/doc/guides/bbdevs/
H A Dturbo_sw.rst25 For the LTE encode operation:
32 For the LTE decode operation:
41 For the 5G NR LDPC encode operation:
47 For the 5G NR LDPC decode operation:
H A Dnull.rst9 the data in the mbuf on which the bbdev operation is to operate and it only
10 works for operation type ``RTE_BBDEV_OP_NONE``.
/dpdk/doc/guides/mempool/
H A Dstack.rst18 The following modes of operation are available for the stack mempool driver and
39 be preempted at any point during a push or pop operation and will not impede
/dpdk/doc/guides/rawdevs/
H A Ddpaa2_qdma.rst21 performing DMA operation.
23 per DMA operation basis.
/dpdk/doc/guides/cryptodevs/features/
H A Dnull.ini8 Sym operation chaining = Y

123456