| /dpdk/drivers/common/cnxk/ |
| H A D | roc_ae.c | 21 .order = {.data = {0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 43 .order = {.data = {0XFF, 0XFF, 0XFF, 0XFF, 0XFF, 0XFF, 0XFF, 66 .order = {.data = {0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00, 0x00, 92 .order = {.data = {0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 123 .order = {.data = {0x01, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF,
|
| H A D | roc_ae.h | 51 } order; member
|
| /dpdk/doc/guides/nics/ |
| H A D | virtio.rst | 244 In-order version for split virtqueue. 247 Regular and in-order version for packed virtqueue. 275 In-order callbacks only work on simulated virtio user vdev. 284 in-order feature. 416 It is used to enable virtio device in-order feature. 448 * `In-order <https://docs.oasis-open.org/virtio/virtio/v1.1/cs01/ 452 driver will use descriptors in order. 471 #. Split virtqueue in-order mergeable path: If Rx mergeable and in-order feature are 473 #. Split virtqueue in-order non-mergeable path: If in-order feature is negotiated and 485 #. Packed virtqueue in-order mergeable path: If in-order and Rx mergeable feature are [all …]
|
| H A D | mvneta.rst | 143 In order to run testpmd example application following command can be used: 151 In order to run l2fwd example application following command can be used:
|
| /dpdk/doc/guides/eventdevs/ |
| H A D | opdl.rst | 10 All packets follow the same path through the device. The order in which\ 11 packets follow is determined by the order in which queues are set up.\ 13 do not go out of order 62 As stated the order in which packets travel through queues is static in 63 nature. They go through the queues in the order the queues are setup at 92 - The order in which packets moved between queues is static and fixed \
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | packet_distrib_lib.rst | 31 #. The worker lcores all share a single cache line with the distributor core in order to pass mess… 42 and that all packets with the same tag are processed in input order. 59 …set of returned packets, all packets sharing the same tag will be returned in their original order. 63 the packets sharing a tag will likely get out of order. 66 who may then flush their buffered packets sooner and cause packets to get out of order. 72 while allowing packet order within a packet flow -- identified by a tag -- to be maintained.
|
| H A D | reorder_lib.rst | 16 The user inserts out of order mbufs into the reorder buffer and pulls in-order 75 library to transmit packets in the same order they were received. 79 The processing of packets by the workers is not guaranteed to be in order, 80 hence a reorder buffer can be used to order as many packets as possible.
|
| H A D | writing_efficient_code.rst | 142 In order to achieve higher throughput, 192 the C11 memory model and provide finer memory order control. 216 in the compare-and-swap operation can be replaced with ACQUIRE memory order. 220 store operation can use RELEASE memory order. 228 can be written with RELAXED memory order. However, the guard variable should 229 be written with RELEASE memory order. This ensures that the store to guard 233 with ACQUIRE memory order. The payload or the data the writer communicated, 234 can be read with RELAXED memory order. This ensures that, if the store to
|
| H A D | lto.rst | 24 need to explicitly initialize variable in order to silence the compiler.
|
| /dpdk/drivers/common/cpt/ |
| H A D | cpt_ucode_asym.h | 493 .order = {.data = {0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 515 .order = {.data = {0XFF, 0XFF, 0XFF, 0XFF, 0XFF, 0XFF, 0XFF, 538 .order = {.data = {0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x00, 0x00, 566 .order = {.data = {0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 601 .order = {.data = {0x01, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 652 order_len = ec_grp[curveid].order.length; in cpt_ecdsa_sign_prep() 688 memcpy(dptr + o_offset, ec_grp[curveid].order.data, order_len); in cpt_ecdsa_sign_prep() 757 order_len = ec_grp[curveid].order.length; in cpt_ecdsa_verify_prep() 799 memcpy(dptr + o_offset, ec_grp[curveid].order.data, order_len); in cpt_ecdsa_verify_prep()
|
| /dpdk/drivers/crypto/armv8/ |
| H A D | rte_armv8_pmd.c | 141 #define CRYPTO_GET_ALGO(order, cop, calg, aalg, keyl) \ argument 144 (crypto_chain_order[(order)])[(cop)]; \ 363 enum armv8_crypto_chain_order order; in armv8_crypto_set_session_chained_parameters() local 372 order = sess->chain_order; in armv8_crypto_set_session_chained_parameters() 428 CRYPTO_GET_ALGO(order, cop, calg, aalg, 128); in armv8_crypto_set_session_chained_parameters()
|
| /dpdk/doc/guides/bbdevs/features/ |
| H A D | default.ini | 5 ; the other driver files and also the order that they appear in
|
| /dpdk/doc/guides/gpus/features/ |
| H A D | default.ini | 5 ; the other driver files and also the order that they appear in
|
| /dpdk/doc/guides/compressdevs/features/ |
| H A D | default.ini | 5 ; the other driver files and also the order that they appear in
|
| /dpdk/doc/guides/tools/ |
| H A D | testeventdev.rst | 211 #. Verify the ingress order maintenance. 240 order queue test operation. 242 The order queue test configures the eventdev with two queues and an event 249 processed in parallel on the different workers, the ingress order of events 252 ingress order(i.e producer ingress order). 278 Example command to run order queue test: 319 order all types queue test operation. 341 Example command to run order ``all types queue`` test:
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | mlx5.rst | 38 In order to move the device to crypto operational mode, credential and KEK 40 The credential will be used by the software in order to perform crypto login, and the KEK is 79 All the device ports should set it in order to move to operational mode.
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | l3_forward_access_ctrl.rst | 69 …The library assumes that each field in the rule is in LSB or Little Endian order when creating the… 70 It internally converts them to MSB or Big Endian order. 71 When performing a lookup, the library assumes the input is in MSB or Big Endian order. 112 * Rules are organized in descending order of priority, 162 As described earlier, the application assume rules are listed in descending order of priority, 318 In order to differentiate the two types of rules, ACL rules add a signature in the userdata field. 319 As for the priority field, the application assumes rules are organized in descending order of prior…
|
| H A D | service_cores.rst | 52 order to register services: ``rte_service_component.h``, in addition 82 To remove a service core, the steps are similar to adding but in reverse order.
|
| /dpdk/doc/guides/eventdevs/features/ |
| H A D | default.ini | 5 ; the other driver files and also the order that they appear in
|
| /dpdk/doc/guides/howto/ |
| H A D | flow_bifurcation.rst | 52 in order to get the flow bifurcation mechanism. 57 In order to define the filters strictly with flow rules,
|
| /dpdk/doc/guides/regexdevs/features/ |
| H A D | default.ini | 5 ; the other driver files and also the order that they appear in
|
| /dpdk/doc/guides/vdpadevs/features/ |
| H A D | default.ini | 5 ; the other driver files and also the order that they appear in
|
| /dpdk/doc/guides/vdpadevs/ |
| H A D | mlx5.rst | 56 arms the CQ in order to get an interrupt event in the next traffic burst. 73 and interrupts are configured to the device in order to notify traffic for the
|
| /dpdk/doc/guides/dmadevs/ |
| H A D | hisilicon.rst | 23 user-space IO driver such as ``vfio-pci`` in order to be used by DPDK.
|
| /dpdk/doc/guides/contributing/ |
| H A D | vulnerability.rst | 41 In order to reduce the disclosure of a vulnerability in the early stages, 125 In order to ensure full traceability, we need a CVE number assigned 147 In order to ensure full traceability, we need a CVE number assigned 302 in order to coordinate the release of fixes
|