Home
last modified time | relevance | path

Searched refs:interfaces (Results 1 – 25 of 52) sorted by relevance

123

/dpdk/doc/guides/sample_app_ug/
H A Dkernel_nic_interface.rst43 KNI interfaces for each physical NIC port. For each physical NIC port,
45 writes to the corresponding KNI interfaces and the other thread reads from
46 the KNI interfaces and writes the data unmodified to the physical NIC port.
76 set to *on*. This sets the carrier state of the KNI interfaces to *on*
77 when the KNI interfaces are enabled without regard to the actual link state
176 four KNI interfaces: ``vEth0_0``/``vEth0_1`` bound to physical port 0 and
216 Linux commands to manage the KNI interfaces as if they were any other
283 In addition, one or more kernel NIC interfaces are allocated for each
286 The code for allocating the kernel NIC interfaces for a specific port is
306 to see if this lcore is reading from or writing to kernel NIC interfaces.
[all …]
H A Dintro.rst42 interfaces are working with DPDK.
/dpdk/app/dumpcap/
H A Dmain.c87 static struct interface_list interfaces = TAILQ_HEAD_INITIALIZER(interfaces); variable
204 TAILQ_INSERT_TAIL(&interfaces, intf, next); in add_interface()
424 TAILQ_FOREACH(intf, &interfaces, next) { in cleanup_pdump_resources()
479 TAILQ_FOREACH(intf, &interfaces, next) { in report_packet_stats()
619 intf = TAILQ_FIRST(&interfaces); in create_output()
681 TAILQ_FOREACH(intf, &interfaces, next) { in enable_pdump()
795 if (TAILQ_EMPTY(&interfaces)) in main()
/dpdk/doc/guides/tools/
H A Ddumpcap.rst42 To list interfaces available for capture, use ``--list-interfaces``.
46 To capture on multiple interfaces at once, use multiple ``-I`` flags.
54 # <build_dir>/app/dpdk-dumpcap --list-interfaces
H A Ddevbind.rst30 Print the current status of all known network interfaces.
/dpdk/doc/guides/nics/
H A Dkni.rst38 Above command will create ``kni0`` and ``kni1`` Linux network interfaces,
39 those interfaces can be controlled by standard Linux tools.
44 There is no hard limit on number of interfaces that can be created.
50 ``librte_kni`` can create Linux network interfaces with different features,
123 * Observe Linux interfaces
H A Dpfe.rst32 high performance Ethernet interfaces. The diagram below shows a
83 net_pfe0 and net_pfe1 are logical ethernet interfaces, created by HIF client
85 host interface and these logical interfaces. PFE ethernet driver is a
87 receive packets from HIF via logical interfaces.
168 to specify port ID. PFE driver supports only two interfaces, so valid values
H A Dvdev_netvsc.rst9 interfaces and associated SR-IOV virtual function (VF) devices found in
85 If nonzero, forces the use of specified interfaces even if not detected as
96 all unrouted NetVSC interfaces found on the system.
H A Dmemif.rst27 The method to enable one or more interfaces is to use the
33 interfaces using same socket, be sure to specify unique ids ``id=0``, ``id=1``,
53 In order to create memif connection, two memif interfaces, each in separate
55 ``client`` role. It is not possible to connect two interfaces in a single
60 memif interfaces. Socket file path is specified at interface creation see
64 multiple interfaces. One process can have ``client`` and ``server`` interfaces
85 (``MEMIF_MSG_TYPE_DISCONNECT``) can be sent by both server and client interfaces at
H A Dtap.rst7 The ``rte_eth_tap.c`` PMD creates a device using TAP interfaces on the
18 These TAP interfaces can be used with Wireshark or tcpdump or Pktgen-DPDK
20 application. The method enable one or more interfaces is to use the
89 interfaces are passed to DPDK ``rte_eal_init`` arguments as ``--vdev=net_tunX``,
202 ``dtap0`` and ``dtap1`` interfaces created.
204 Next set the links for the two interfaces to up via the commands below::
209 Then use socat to create a loopback for the two interfaces::
H A Dcxgbe.rst421 #. Get the PCI bus addresses of the interfaces bound to cxgb4 driver:
436 Both the interfaces of a Chelsio 2-port adapter are bound to the
498 #. Get the PCI bus addresses of the interfaces bound to cxgb4 driver:
513 Both the interfaces of a Chelsio 2-port adapter are bound to the
529 #. Bring up the interfaces:
715 #. Get the PCI bus addresses of the interfaces bound to t5nex driver:
731 Both the interfaces of a Chelsio 2-port adapter are bound to the
H A Ddpaa.rst36 interfaces and accelerators by multiple CPU cores, and the accelerators
136 The Ethernet driver is bound to a FMAN port and implements the interfaces
158 - Using standard Mempools operations RTE API, the mempool driver interfaces
309 direct ioctl based interfaces for FMAN configuration as used by the FMC tool
H A Dmlx4.rst40 This capability allows the PMD to coexist with kernel network interfaces
80 - librte_net_mlx4 brings kernel network interfaces up during initialization
84 - **ethtool** operations on related kernel interfaces also affect the PMD.
180 - mlx4_en: Ethernet device driver that provides kernel network interfaces.
372 #. Make sure Ethernet interfaces are in working order and linked to kernel
H A De1000em.rst120 backed up with two TAP networking host interfaces, tapvm01 and tapvm02.
128 #. Configure your TAP networking interfaces using ip/ifconfig tools.
H A Dfm10k.rst117 interfaces. The FM10000 PMD only manages host interfaces. For the
H A Ddpaa2.rst45 interfaces, an L2 switch, or accelerator instances.
47 The MC provides memory-mapped I/O command interfaces (MC portals)
98 in creating a network interfaces.
215 DPIO (Datapath I/O): provides interfaces to enqueue and dequeue
388 interfaces needed to connect the DPAA2 network interface to
H A Dthunderx.rst235 If a system has three interfaces, a total of 18 VF devices will be created
283 We want to bind two physical interfaces with 24 queues each device, we attach two primary VFs
284 and four secondary VFs. In our example we choose two 10G interfaces eth1 (0002:01:00.2) and eth2 (0…
H A Denetfec.rst82 - Then Tx is done first followed by Rx via logical interfaces.
H A Dmvneta.rst136 Additionally interfaces used by DPDK application need to be put up:
/dpdk/doc/guides/prog_guide/
H A Dkernel_nic_interface.rst13 * Faster than existing Linux TUN/TAP interfaces
74 disabled, and the default carrier state of KNI interfaces is set to *off*.
120 This mode will create only one kernel thread for all KNI interfaces to
153 The default carrier state of KNI interfaces created by the ``rte_kni``
185 of KNI interfaces will be set to *off*.
241 Before any KNI interfaces can be created, the ``rte_kni`` kernel module must
244 The KNI interfaces are created by a DPDK application dynamically via the
256 allow DPDK applications to perform actions when the KNI interfaces are
316 The KNI interfaces can be deleted by a DPDK application with
317 ``rte_kni_release()``. All KNI interfaces not explicitly deleted will be
H A Drawdev.rst83 interfaces
H A Dstack_lib.rst29 Both types use the same set of interfaces, but their implementations differ.
/dpdk/examples/ip_pipeline/examples/
H A Dtap.cli17 ; Configure Linux kernel bridge between TAP0 and TAP1 interfaces:
H A Dkni.cli20 ; Configure Linux kernel bridge between KNI0 and KNI1 interfaces:
/dpdk/doc/guides/howto/
H A Dpacket_capture_framework.rst34 from one or more interfaces and writes them to a file in Pcapng format.

123