| /dpdk/doc/guides/howto/ |
| H A D | debug_troubleshoot.rst | 39 :numref:`dtg_sample_app_model`. 61 RX Port and associated core :numref:`dtg_rx_rate`. 110 RX-TX port and associated cores :numref:`dtg_rx_tx_drop`. 148 Producer point for ring :numref:`dtg_producer_ring`. 170 Consumer point for ring :numref:`dtg_consumer_ring`. 192 Memory objects close to NUMA :numref:`dtg_mempool`. 247 Crypto device and PMD :numref:`dtg_crypto`. 289 Custom worker function :numref:`dtg_distributor_worker`. 324 service functions on service cores :numref:`dtg_service`. 379 Traffic Manager on TX interface :numref:`dtg_qos_tx`. [all …]
|
| H A D | virtio_user_for_container_networking.rst | 13 :numref:`figure_use_models_for_running_dpdk_in_containers`. 31 in :numref:`figure_virtio_user_for_container_networking`.
|
| H A D | packet_capture_framework.rst | 74 :numref:`figure_packet_capture_framework`. 87 Rx side packets on dpdk_port0 in :numref:`figure_packet_capture_framework` and
|
| H A D | virtio_user_as_exceptional_path.rst | 35 in :numref:`figure_virtio_user_as_exceptional_path`.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | efd_lib.rst | 53 In this scheme (:numref:`figure_efd1`), the front end server/distributor/load balancer 66 computation-based schemes is ``consistent hashing``, shown in :numref:`figure_efd2`. 98 As shown in :numref:`figure_efd3`, when doing a lookup, the flow-table 127 input key to the correct value is found, as shown in :numref:`figure_efd4`. 143 impossible, as a result EFD, as shown in :numref:`figure_efd5`, 168 :numref:`figure_efd6` shows an example of using EFD as a flow-level load 321 :numref:`figure_efd7` depicts the group assignment for 7 flow keys as an example. 346 as shown in :numref:`figure_efd9`. 379 :numref:`figure_efd11` depicts the lookup operation for EFD. Given an input key, 408 :numref:`figure_efd12` depicts the high level idea of group rebalancing, given an [all …]
|
| H A D | rib_lib.rst | 30 Internally RIB is represented as a binary tree as shown in :numref:`figure_rib_internals`: 69 Given a RIB structure with the routes depicted in :numref:`figure_rib_internals`, 95 (yellow triangle in :numref:`figure_rib_internals`): 122 shown in :numref:`figure_rib_pic`. Every route can have a feasible next hop
|
| H A D | mempool_lib.rst | 49 :numref:`figure_memory-management` and :numref:`figure_memory-management2`. 94 :numref:`figure_mempool` shows a cache in operation.
|
| H A D | packet_framework.rst | 42 An example of packet processing pipeline is presented in :numref:`figure_figure32`: 58 :numref:`table_qos_19` is a non-exhaustive list of ports that can be implemented with the Packet Fr… 144 :numref:`table_qos_21` is a non-exhaustive list of types of tables that can be implemented with the… 215 The table abstract interface is described in :numref:`table_qos_29_1`. 371 :numref:`table_qos_22` lists the hash table configuration parameters shared by all different hash t… 534 :numref:`figure_figure34`, :numref:`table_qos_25` and :numref:`table_qos_26` detail the main data s… 607 :numref:`figure_figure35` and :numref:`table_qos_27` detail the bucket search pipeline stages (eith… 711 The key signature comparison logic is described in :numref:`table_qos_28`. 808 :numref:`figure_figure37`, :numref:`figure_figure38`, :numref:`table_qos_30` and :numref:`table_qos… 1021 :numref:`table_qos_33` lists the next hop actions. [all …]
|
| H A D | qos_framework.rst | 129 The scheduling hierarchy is shown in :numref:`figure_sched_hier_per_port`. 590 … bucket generic parameters and operations are presented in :numref:`table_qos_6` and :numref:`tabl… 632 the current design uses the persistent data structure presented in :numref:`table_qos_8`, 633 while the implementation of the token bucket operations is described in :numref:`table_qos_9`. 752 as described in :numref:`table_qos_10` and :numref:`table_qos_11`. 1017 :numref:`table_qos_14` and :numref:`table_qos_15` illustrates the watermark operation. 1167 :numref:`figure_blk_diag_dropper` illustrates how the dropper integrates with the scheduler. 1199 The flow through the dropper is illustrated in :numref:`figure_flow_tru_dropper`. 1238 A RED configuration contains the parameters given in :numref:`table_qos_16`. 1271 A PIE configuration contains the parameters given in :numref:`table_qos_16a`. [all …]
|
| H A D | toeplitz_hash_lib.rst | 75 Toeplitz hash function. In figure :numref:`figure_rss_queue_assign` only a few 219 lcores, as shown in :numref:`figure_predictable_snat_1`: 244 shown in :numref:`figure_predictable_snat_2`:
|
| H A D | traffic_metering_and_policing.rst | 107 specified per color as show in :numref:`figure_rte_mtr_chaining`.
|
| H A D | generic_segmentation_offload_lib.rst | 94 in :numref:`figure_gso-output-segment-format`. 129 :numref:`figure_gso-three-seg-mbuf` illustrates an example of a three-part
|
| H A D | mbuf_lib.rst | 46 :numref:`figure_mbuf1` and :numref:`figure_mbuf2` show some of these scenarios.
|
| H A D | fib_lib.rst | 102 The lookup algorithms logic can be seen in :numref:`figure_dir_24_8_alg`:
|
| H A D | kernel_nic_interface.rst | 20 The components of an application using the DPDK Kernel NIC Interface are shown in :numref:`figure_k… 328 :numref:`figure_pkt_flow_kni` shows a typical scenario with packets sent in both directions.
|
| H A D | generic_receive_offload_lib.rst | 112 :numref:`figure_gro-key-algorithm` illustrates the procedure of the
|
| /dpdk/doc/guides/platform/ |
| H A D | cnxk.rst | 25 The :numref:`figure_cnxk_resource_virtualization` diagram depicts the 43 The :numref:`table_cnxk_rvu_dpdk_mapping` shows the various local 92 The :numref:`figure_cnxk_resource_virtualization` diagram also shows a 138 The :numref:`figure_cnxk_packet_flow_hw_accelerators` diagram depicts
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | l2_forward_real_virtual.rst | 32 …sed to benchmark performance using a traffic-generator, as shown in the :numref:`figure_l2_fwd_ben… 33 or in a virtualized environment as shown in :numref:`figure_l2_fwd_virtenv_benchmark_setup`. 47 This application may be used for basic VM to VM communication as shown in :numref:`figure_l2_fwd_vm…
|
| H A D | l2_forward_job_stats.rst | 31 …sed to benchmark performance using a traffic-generator, as shown in the :numref:`figure_l2_fwd_ben… 33 The application can also be used in a virtualized environment as shown in :numref:`figure_l2_fwd_vi…
|
| H A D | dist_app.rst | 67 How these threads work together is shown in :numref:`figure_dist_app` below.
|
| H A D | vmdq_dcb_forwarding.rst | 26 …es the VMDQ feature to have 32 pools with 4 queues each as indicated in :numref:`figure_vmdq_dcb_e…
|
| H A D | test_pipeline.rst | 58 :numref:`table_test_pipeline_1` describes the table types used and how they are populated.
|
| /dpdk/doc/guides/tools/ |
| H A D | testeventdev.rst | 386 number of stages as mentioned in :numref:`table_eventdev_perf_queue_test`. 514 producers as mentioned in :numref:`table_eventdev_perf_atq_test`. 620 and number of stages as mentioned in :numref:`table_eventdev_pipeline_queue_test`. 747 and number of stages as mentioned in :numref:`table_eventdev_pipeline_atq_test`.
|
| /dpdk/doc/guides/contributing/ |
| H A D | documentation.rst | 491 * Images can then be linked to using the ``:numref:`` directive:: 493 The mempool layout is shown in :numref:`figure_mempool`. 497 **Note**: The ``:numref:`` directive requires Sphinx 1.3.1 or later. 535 * Tables can be linked to using the ``:numref:`` and ``:ref:`` directives, as shown in the previous… 538 The QOS configuration is shown in :numref:`table_qos_pipes`.
|
| /dpdk/doc/guides/nics/ |
| H A D | intel_vf.rst | 25 Refer to :numref:`figure_single_port_nic`. 27 Therefore, a NIC is logically distributed among multiple virtual machines (as shown in :numref:`fig… 561 …* The Virtual Machine Monitor (see :numref:`figure_perf_benchmark`) is equivalent to a Host OS w… 583 :numref:`figure_fast_pkt_proc` shows the scenario where some VMs directly communicate externally vi… 602 :numref:`figure_inter_vm_comms` shows an example.
|