| /dpdk/doc/guides/eventdevs/ |
| H A D | cnxk.rst | 108 connected to event device. 206 Using the same mempool for all the ethernet device ports connected to 210 ethernet devices connected to event device to override this applications can 213 connected to event device.
|
| /dpdk/doc/guides/nics/ |
| H A D | nfb.rst | 91 Although each slot may be connected to a different CPU and therefore to a different 101 Since a card is always represented as a single port, but can be connected to two 102 NUMA nodes, there is need for manual check where master/slave is connected.
|
| H A D | memif.rst | 18 the shared memory. Each interface can be connected to one peer interface 56 process. Each interface can be connected to one interface at same time, 71 connected socket (control channel). Then it sends the 'hello' message 84 'connected' message (``MEMIF_MSG_TYPE_CONNECTED``). Disconnect 279 In this example we will create 2 memif ports connected into loopback.
|
| H A D | vmxnet3.rst | 15 #. Vmxnet3 with a native NIC connected to a vSwitch 17 #. Vmxnet3 chaining VMs connected to a vSwitch
|
| H A D | ipn3ke.rst | 13 Controllers are connected to CPU with PCIe Gen3x16 Switch, all the
|
| H A D | enetc.rst | 64 - RTE framework scans the PCI bus for connected devices.
|
| H A D | enic.rst | 421 VLAN tagged by software. If the adapter is connected to a properly configured 425 connected point-to-point to another adapter port or connected though a router 449 - Requires VM-FEX, and so is only available on UCS managed servers connected 546 - SR-IOV on UCS managed servers connected to Fabric Interconnects
|
| H A D | mlx4.rst | 307 2. Use the CPU near local NUMA node to which the PCIe adapter is connected, 313 to identify the NUMA node to which the PCIe adapter is connected.
|
| /dpdk/drivers/net/memif/ |
| H A D | memif.h | 143 memif_msg_connected_t connected; member
|
| H A D | memif_socket.c | 356 memif_msg_connected_t *c = &msg->connected; in memif_msg_receive_connected() 499 c = &e->msg.connected; in memif_msg_enq_connected()
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | flow_filtering.rst | 123 For this example we are configuring number of rx and tx queues that are connected 128 :start-after: Configuring number of RX and TX queues connected to single port. 8< 129 :end-before: >8 End of Configuring RX and TX queues connected to single port.
|
| H A D | kernel_nic_interface.rst | 79 mode where the NIC port may not be physically connected to anything. 198 to be connected in order to use the KNI interface. One KNI interface
|
| H A D | l2_forward_event.rst | 319 Ethernet port's Rx queues are connected to its respective event queue at 321 connected via Tx adapter.
|
| /dpdk/drivers/vdpa/mlx5/ |
| H A D | mlx5_vdpa.c | 273 if (!priv->connected) in mlx5_vdpa_dev_close() 299 priv->connected = true; in mlx5_vdpa_dev_config() 442 priv->connected = false; in mlx5_vdpa_dev_cleanup()
|
| H A D | mlx5_vdpa.h | 125 bool connected; member
|
| /dpdk/doc/guides/howto/ |
| H A D | lm_virtio_vhost_user.rst | 26 The NIC's on both servers are connected to a switch 27 which is also connected to the traffic generator.
|
| H A D | telemetry.rst | 51 #. When connected, the script displays the following, waiting for user input::
|
| H A D | lm_bond_virtio_sriov.rst | 30 The NIC's on both servers are connected to a switch 31 which is also connected to the traffic generator.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | event_crypto_adapter.rst | 168 combination. This API provides whether cryptodev and eventdev are connected using 308 The eventdev to which the event_crypto_adapter is connected needs to
|
| H A D | telemetry_lib.rst | 9 connection, taking requests from a connected client and replying with the JSON
|
| H A D | overview.rst | 104 and/or execution blocks connected together on a logical core.
|
| H A D | graph_lib.rst | 107 The number of downstream nodes connected to this node. The ``next_nodes[]`` 116 The dynamic array to store the downstream nodes connected to this node. Downstream
|
| /dpdk/doc/guides/bbdevs/ |
| H A D | la12xx.rst | 57 - NXP LA1224 PCIe Modem card connected to ARM host.
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_2_2.rst | 255 * **e1000/base: Prevent ULP flow if cable connected.** 257 Enabling ULP on link down when the cable is connected caused an infinite 324 are random and intermittent link losses when 82579 is connected to specific
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | nic_perf_intel_platform.rst | 83 …I slots always check the caption, such as CPU0 or CPU1 to indicate which socket it is connected to.
|