| /dpdk/doc/guides/howto/ |
| H A D | debug_troubleshoot.rst | 20 consolidate a few commonly seen issues for reference. Then, isolate to identify 79 * Make use of ``rte_eth_dev_stats`` to identify the drops cause. 131 * If the TX rate is falling behind the application fill rate, identify if 308 * Identify core role using ``rte_eal_lcore_role`` to identify RTE, OFF, 371 * Periodically checks stats for queue and port to identify the starvation.
|
| /dpdk/drivers/net/ionic/ |
| H A D | ionic_dev.c | 119 .identify.opcode = IONIC_CMD_IDENTIFY, in ionic_dev_cmd_identify() 120 .identify.ver = ver, in ionic_dev_cmd_identify()
|
| H A D | ionic_if.h | 2686 struct ionic_dev_identify_cmd identify; member 2721 struct ionic_dev_identify_comp identify; member
|
| /dpdk/doc/guides/nics/ |
| H A D | netvsc.rst | 51 The first step is to identify the network device to override. 53 (`UUID`_) to identify devices on the bus similar to how PCI uses Domain:Bus:Function.
|
| H A D | memif.rst | 31 messages. Each memif has a unique id per socket. This id is used to identify 41 "id=0", "Used to identify peer interface", "0", "uint32_t" 180 This limitation is in place, because it is too expensive to identify memseg
|
| H A D | ipn3ke.rst | 50 Acceleration, so users need to identify which Acceleration is used. Current IPN3KE can
|
| H A D | igc.rst | 68 The Flow Director works in receive mode to identify specific flows or sets of flows and route
|
| H A D | hns3.rst | 173 The Flow Director works in receive mode to identify specific flows or sets of
|
| H A D | i40e.rst | 357 The Flow Director works in receive mode to identify specific flows or sets of flows and route them … 754 Users should consult the release notes specific to a DPDK release to identify
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | octeontx.rst | 96 identify the VFs. To be accessible from DPDK, VFs need to be bound to vfio-pci
|
| /dpdk/examples/pipeline/examples/ |
| H A D | selector.spec | 25 ; destination IP address fields. The member_id produced by the selector table is used to identify
|
| /dpdk/drivers/net/ngbe/base/ |
| H A D | ngbe_phy.c | 407 err = phy->identify(hw); in ngbe_init_phy()
|
| H A D | ngbe_dummy.h | 327 hw->phy.identify = ngbe_phy_identify_dummy; in ngbe_init_ops_dummy()
|
| H A D | ngbe_type.h | 343 s32 (*identify)(struct ngbe_hw *hw); member
|
| /dpdk/doc/guides/bbdevs/ |
| H A D | la12xx.rst | 61 * Use dev arg option ``modem=0`` to identify the modem instance for a given
|
| /dpdk/drivers/net/ixgbe/base/ |
| H A D | ixgbe_82598.c | 171 phy->ops.identify(hw); in ixgbe_init_phy_ops_82598() 1207 hw->phy.ops.identify(hw); in ixgbe_get_supported_physical_layer_82598()
|
| H A D | ixgbe_82599.c | 109 ret_val = phy->ops.identify(hw); in ixgbe_init_phy_ops_82599() 301 phy->ops.identify = ixgbe_identify_phy_82599; in ixgbe_init_ops_82599() 2163 hw->phy.ops.identify(hw); in ixgbe_get_supported_physical_layer_82599()
|
| H A D | ixgbe_x550.c | 634 phy->ops.identify = ixgbe_identify_phy_fw; in ixgbe_init_ops_X550EM() 640 phy->ops.identify = ixgbe_identify_phy_x550em; in ixgbe_init_ops_X550EM() 644 phy->ops.identify = ixgbe_identify_phy_x550em; in ixgbe_init_ops_X550EM() 2301 ret_val = phy->ops.identify(hw); in ixgbe_init_phy_ops_X550em() 3616 hw->phy.ops.identify(hw); in ixgbe_get_supported_physical_layer_X550em()
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | deprecation.rst | 61 Need to identify this kind of usages and fix in 20.11, otherwise this blocks
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | dist_app.rst | 117 SST-BF cores are present in the core mask, the application will identify these
|
| H A D | l3_forward.rst | 38 to identify the next hop for each input packet at runtime. 236 If errors are detected, the application exits with messages to identify the errors encountered.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | rte_security.rst | 129 This will allow the application to identify the security processing 556 Session APIs need a parameter ``rte_security_ctx`` to identify the crypto/ethernet
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | build_dpdk.rst | 63 used, for example, to identify any missing required packages for a driver.
|
| /dpdk/drivers/net/txgbe/base/ |
| H A D | txgbe_dummy.h | 625 hw->phy.identify = txgbe_phy_identify_dummy; in txgbe_init_ops_dummy()
|
| H A D | txgbe_type.h | 638 s32 (*identify)(struct txgbe_hw *hw); member
|