| /dpdk/drivers/net/mlx5/ |
| H A D | mlx5_tx.c | 93 int seen = check_err_cqe_seen(err_cqe); in mlx5_tx_error_cqe_handle() local 95 if (!seen && txq_ctrl->dump_file_n < in mlx5_tx_error_cqe_handle() 119 if (!seen) in mlx5_tx_error_cqe_handle()
|
| /dpdk/doc/guides/nics/ |
| H A D | overview.rst | 14 The interface seen in the virtual environment is a VF (Virtual Function).
|
| H A D | nfp.rst | 119 NFP ports belonging to same PF can be seen inside PMD initialization with a 121 0000:03:00.0 and four ports is seen by the PMD code as:
|
| H A D | enic.rst | 171 seen on the VM instance and should be available for binding to a DPDK.
|
| /dpdk/doc/guides/howto/ |
| H A D | lm_bond_virtio_sriov.rst | 160 VF traffic is seen at P1 and P2. 176 No VF traffic is seen at P0 and P2, VF MAC address still present. 194 No VF traffic is seen at P0 and P2. 354 VF traffic is seen at P1 (VF) and P2 (Bonded device). 369 VF traffic is seen at P1 (VF) and P2 (Bonded device).
|
| H A D | debug_troubleshoot.rst | 20 consolidate a few commonly seen issues for reference. Then, isolate to identify 97 #. Is there drops still seen? 102 * If there are drops seen for RX adapter or RX distributor, try using
|
| H A D | lm_virtio_vhost_user.rst | 125 Virtio traffic is seen at P1 and P2. 249 Virtio traffic is seen at P0 and P1.
|
| /dpdk/drivers/net/vhost/ |
| H A D | rte_eth_vhost.c | 136 bool seen[RTE_MAX_QUEUES_PER_PORT * 2]; member 892 state->seen[i] = false; in destroy_device() 1086 if (state->cur[idx] != state->seen[idx]) { in rte_eth_vhost_get_queue_event() 1087 state->seen[idx] = state->cur[idx]; in rte_eth_vhost_get_queue_event()
|
| /dpdk/drivers/net/mlx4/ |
| H A D | mlx4_flow.c | 148 uint64_t seen = 0; in mlx4_conv_rss_types() local 159 seen |= types & in[i]; in mlx4_conv_rss_types() 163 !(types & ~seen)) in mlx4_conv_rss_types()
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | fib_lib.rst | 102 The lookup algorithms logic can be seen in :numref:`figure_dir_24_8_alg`:
|
| H A D | compressdev.rst | 112 acceleration and CPU features. List of compression device features can be seen in the 117 features can be seen in the RTE_COMP_FF_XXX macros.
|
| H A D | switch_representation.rst | 296 In the following diagram, each meaningful traffic origin or endpoint as seen 470 sense when the traffic in question is normally seen (i.e. sent or received)
|
| H A D | lpm6_lib.rst | 54 The implementation can be seen as a multi-bit trie where the *stride*
|
| H A D | rte_flow.rst | 2897 set, unpredictable value will be seen depending on driver implementation. For 3216 | ``live_connection`` | one ack was seen for this connection | 3260 | ``sent_end`` | max{seq + len} seen in sent packets | 3262 | ``reply_end`` | max{sack + max{win, 1}} seen in reply packets | 3264 | ``max_win`` | max{max{win, 1}} + {sack - ack} seen in sent packets | 3266 | ``max_ack`` | max{ack} + seen in sent packets |
|
| H A D | efd_lib.rst | 201 exact matched with the input key to rule out new never seen before
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | build_dpdk.rst | 92 Many of these options come from the "meson" tool itself and can be seen documented on the
|
| /dpdk/doc/guides/dmadevs/ |
| H A D | idxd.rst | 46 An example of how this may be done can be seen in the script ``dpdk_idxd_cfg.py``
|
| /dpdk/doc/guides/freebsd_gsg/ |
| H A D | build_dpdk.rst | 154 Currently loaded modules can be seen by using the ``kldstat`` command and a module
|
| /dpdk/doc/guides/faq/ |
| H A D | faq.rst | 15 The number of pages allocated can be seen by executing the following command::
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | ip_pipeline.rst | 19 …d mapping the pipelines to execution threads are endless, therefore this application can be seen as
|
| H A D | multi_process.rst | 139 such as a client-server mode of operation seen in the next example,
|
| H A D | l3_forward.rst | 330 the full setup function including the IPv6 setup can be seen in the app code.
|
| /dpdk/doc/guides/rawdevs/ |
| H A D | ioat.rst | 65 An example of how this may be done can be seen in the script ``dpdk_idxd_cfg.py``
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_16_07.rst | 196 enabled the ``CONFIG_IO_STRICT_DEVMEM`` option. The error seen by the
|
| H A D | release_18_11.rst | 357 and seen as invalid because of its state ``RTE_ETH_DEV_UNUSED``.
|