Home
last modified time | relevance | path

Searched refs:interface (Results 1 – 25 of 136) sorted by relevance

123456

/dpdk/doc/guides/nics/
H A Dmemif.rst18 the shared memory. Each interface can be connected to one peer interface
25 interface.
32 peer interface. If you are connecting multiple
41 "id=0", "Used to identify peer interface", "0", "uint32_t"
56 process. Each interface can be connected to one interface at same time,
76 interface. If such interface is found, 'ack' message (``MEMIF_MSG_TYPE_ACK``) is
215 First create ``server`` interface::
223 You can also enable ``zero-copy`` on ``client`` interface::
247 vpp# create interface memif id 0 server no-zero-copy
248 vpp# set interface state memif0/0 up
[all …]
H A Dpcap_ring.rst72 …The driver reads packets from the given interface using the Linux kernel driver for that interface.
74 The value is an interface name.
79 …The driver reads packets from the given interface using the Linux kernel driver for that interface.
81 The value is an interface name.
86 … The driver sends packets to the given interface using the Linux kernel driver for that interface.
87 The value is an interface name.
93 The value is an interface name.
100 - Use PCAP interface physical MAC
169 Enable 2 tx queues on a network interface:
177 Read only incoming packets from a network interface and write them back to the same network interfa…
[all …]
H A Dkni.rst10 any forwarding application can use PMD interface for KNI.
12 Sending packets to any DPDK controlled interface or sending to the
16 will create ``kni#`` Linux virtual network interface.
20 Packets sent to the KNI Linux interface will be received by the DPDK
22 or to a virtual device (like another KNI interface or PCAP interface).
41 When testpmd forwarding starts, any packets sent to ``kni0`` interface
42 forwarded to the ``kni1`` interface and vice versa.
47 Default interface configuration
68 ``no_request_thread``, by default PMD creates a pthread for each KNI interface
69 to handle Linux network interface control commands, like ``ifconfig kni0 up``
H A Daf_packet.rst24 * ``iface`` - name of the Kernel interface to attach to (required);
56 * A Kernel bound interface to attach to (e.g. a tap interface).
58 Set up an af_packet interface
61 The following example will set up an af_packet interface in DPDK with the
H A Dtap.rst9 device interface on the host and in the DPDK application.
13 local host using a TAP interface. When the TAP PMD is initialized it will
22 ``--vdev=net_tap1`` option given will create an interface named dtap0, dtap1,
25 The interface name can be changed by adding the ``iface=foo0``, for example::
36 for each interface string containing ``mac=fixed``. The MAC address is formatted
63 interface using the standard rx_burst/tx_burst APIs in DPDK. From the host
69 If you need the interface as a real network interface meaning running and has
83 to address the interface using an IP address assigned to the internal
84 interface.
95 options. Default interface name is ``dtunX``, where X stands for unique id.
[all …]
/dpdk/doc/guides/howto/
H A Drte_flow.rst81 iface='some interface', count=1)
83 iface='some interface', count=1)
100 iface='some interface', count=1)
102 iface='some interface', count=1)
179 iface='some interface', count=1)
181 iface='some interface', count=1)
183 iface='some interface', count=1)
201 iface='some interface', count=1)
203 iface='some interface', count=1)
205 iface='some interface', count=1)
[all …]
/dpdk/drivers/net/nfp/nfpcore/
H A Dnfp_cpp.h21 uint32_t interface; member
137 void nfp_cpp_interface_set(struct nfp_cpp *cpp, uint32_t interface);
263 #define NFP_CPP_INTERFACE_TYPE_of(interface) (((interface) >> 12) & 0xf) argument
270 #define NFP_CPP_INTERFACE_UNIT_of(interface) (((interface) >> 8) & 0xf) argument
277 #define NFP_CPP_INTERFACE_CHANNEL_of(interface) (((interface) >> 0) & 0xff) argument
H A Dnfp_mutex.c15 #define MUTEX_LOCKED(interface) ((((uint32_t)(interface)) << 16) | 0x000f) argument
16 #define MUTEX_UNLOCK(interface) (0 | 0x0000) argument
295 uint16_t interface = nfp_cpp_interface(cpp); in nfp_cpp_mutex_unlock() local
316 if (value != MUTEX_LOCKED(interface)) { in nfp_cpp_mutex_unlock()
321 err = nfp_cpp_writel(cpp, muw, mutex->address, MUTEX_UNLOCK(interface)); in nfp_cpp_mutex_unlock()
/dpdk/doc/guides/rel_notes/
H A Drelease_17_02.rst339 * Host interface: PCI Express 3.0 x8
345 * Host interface: PCI Express 3.0 x8
351 * Host interface: PCI Express 3.0 x8
357 * Host interface: PCI Express 3.0 x8
363 * Host interface: PCI Express 3.0 x8
369 * Host interface: PCI Express 3.0 x8
381 * Host interface: PCI Express 3.0 x8
387 * Host interface: PCI Express 3.0 x8
411 * Host interface: PCI Express 3.0 x8
417 * Host interface: PCI Express 3.0 x8
[all …]
H A Drelease_18_08.rst345 * Host interface: PCI Express 3.0 x8
351 * Host interface: PCI Express 3.0 x8
357 * Host interface: PCI Express 3.0 x8
363 * Host interface: PCI Express 3.0 x8
369 * Host interface: PCI Express 3.0 x8
375 * Host interface: PCI Express 3.0 x8
387 * Host interface: PCI Express 3.0 x8
393 * Host interface: PCI Express 3.0 x8
418 * Host interface: PCI Express 3.0 x8
424 * Host interface: PCI Express 3.0 x8
[all …]
H A Drelease_17_05.rst546 * Host interface: PCI Express 3.0 x8
552 * Host interface: PCI Express 3.0 x8
558 * Host interface: PCI Express 3.0 x8
564 * Host interface: PCI Express 3.0 x8
570 * Host interface: PCI Express 3.0 x8
576 * Host interface: PCI Express 3.0 x8
588 * Host interface: PCI Express 3.0 x8
594 * Host interface: PCI Express 3.0 x8
618 * Host interface: PCI Express 3.0 x8
624 * Host interface: PCI Express 3.0 x8
[all …]
H A Drelease_19_02.rst403 * Host interface: PCI Express 3.0 x8
409 * Host interface: PCI Express 3.0 x8
415 * Host interface: PCI Express 3.0 x8
421 * Host interface: PCI Express 3.0 x8
427 * Host interface: PCI Express 3.0 x8
433 * Host interface: PCI Express 3.0 x8
445 * Host interface: PCI Express 3.0 x8
451 * Host interface: PCI Express 3.0 x8
476 * Host interface: PCI Express 3.0 x8
482 * Host interface: PCI Express 3.0 x8
[all …]
H A Drelease_19_05.rst156 * Added SXGMII interface support.
464 * Host interface: PCI Express 3.0 x8
470 * Host interface: PCI Express 3.0 x8
476 * Host interface: PCI Express 3.0 x8
482 * Host interface: PCI Express 3.0 x8
488 * Host interface: PCI Express 3.0 x8
494 * Host interface: PCI Express 3.0 x8
506 * Host interface: PCI Express 3.0 x8
512 * Host interface: PCI Express 3.0 x8
537 * Host interface: PCI Express 3.0 x8
[all …]
H A Drelease_18_02.rst386 * Host interface: PCI Express 3.0 x8
392 * Host interface: PCI Express 3.0 x8
398 * Host interface: PCI Express 3.0 x8
404 * Host interface: PCI Express 3.0 x8
410 * Host interface: PCI Express 3.0 x8
416 * Host interface: PCI Express 3.0 x8
428 * Host interface: PCI Express 3.0 x8
434 * Host interface: PCI Express 3.0 x8
459 * Host interface: PCI Express 3.0 x8
465 * Host interface: PCI Express 3.0 x8
[all …]
H A Drelease_20_08.rst415 * Host interface: PCI Express 3.0 x8
421 * Host interface: PCI Express 3.0 x8
427 * Host interface: PCI Express 3.0 x8
433 * Host interface: PCI Express 3.0 x8
439 * Host interface: PCI Express 3.0 x16
445 * Host interface: PCI Express 3.0 x16
451 * Host interface: PCI Express 3.0 x16
457 * Host interface: PCI Express 4.0 x16
471 * Host interface: PCI Express 3.0 x16
536 * Host interface: PCI Express 3.0 x8
[all …]
H A Drelease_19_08.rst486 * Host interface: PCI Express 3.0 x8
492 * Host interface: PCI Express 3.0 x8
498 * Host interface: PCI Express 3.0 x8
504 * Host interface: PCI Express 3.0 x8
510 * Host interface: PCI Express 3.0 x8
516 * Host interface: PCI Express 3.0 x8
528 * Host interface: PCI Express 3.0 x8
534 * Host interface: PCI Express 3.0 x8
559 * Host interface: PCI Express 3.0 x8
565 * Host interface: PCI Express 3.0 x8
[all …]
H A Drelease_18_11.rst149 MAC address of the selected PCAP interface.
380 Note interface should be ``up`` to be able to read/write sysfs interface.
614 * Host interface: PCI Express 3.0 x8
620 * Host interface: PCI Express 3.0 x8
626 * Host interface: PCI Express 3.0 x8
632 * Host interface: PCI Express 3.0 x8
638 * Host interface: PCI Express 3.0 x8
644 * Host interface: PCI Express 3.0 x8
656 * Host interface: PCI Express 3.0 x8
662 * Host interface: PCI Express 3.0 x8
[all …]
H A Drelease_21_02.rst386 * Host interface: PCI Express 3.0 x8
392 * Host interface: PCI Express 3.0 x8
398 * Host interface: PCI Express 3.0 x8
404 * Host interface: PCI Express 3.0 x8
410 * Host interface: PCI Express 3.0 x16
416 * Host interface: PCI Express 3.0 x16
422 * Host interface: PCI Express 3.0 x16
440 * Host interface: PCI Express 4.0 x8
448 * Host interface: PCI Express 3.0 x16
485 * Host interface: PCI Express 3.0 x8
[all …]
H A Drelease_17_08.rst360 * Host interface: PCI Express 3.0 x8
366 * Host interface: PCI Express 3.0 x8
372 * Host interface: PCI Express 3.0 x8
378 * Host interface: PCI Express 3.0 x8
384 * Host interface: PCI Express 3.0 x8
390 * Host interface: PCI Express 3.0 x8
396 * Host interface: PCI Express 3.0 x16
402 * Host interface: PCI Express 3.0 x8
408 * Host interface: PCI Express 3.0 x8
433 * Host interface: PCI Express 3.0 x8
[all …]
H A Drelease_16_11.rst373 * Host interface: PCI Express 3.0 x8
380 * Host interface: PCI Express 3.0 x8
387 * Host interface: PCI Express 3.0 x8
394 * Host interface: PCI Express 3.0 x8
401 * Host interface: PCI Express 3.0 x8
408 * Host interface: PCI Express 3.0 x16
415 * Host interface: PCI Express 3.0 x8
422 * Host interface: PCI Express 3.0 x8
429 * Host interface: PCI Express 3.0 x16
450 * Host interface: PCI Express 3.0 x8
[all …]
/dpdk/doc/guides/sample_app_ug/
H A Dkernel_nic_interface.rst49 The application can be configured with more than one KNI interface for
65 KNI interface(s) to match the physical NIC port's state. This means that
125 network interface to match it. This means that the KNI interface will
166 interface ``vEth1_0`` with the kernel thread bound to lcore 9.
179 The kernel thread for each interface will be bound as follows:
198 to be connected in order to use the KNI interface. One KNI interface
199 ``vEth0_0`` is created for port 0 and one KNI interface ``vEth1_0`` is
217 Linux network interface.
219 Enable KNI interface and assign an IP address:
225 Show KNI interface configuration and statistics:
[all …]
H A Dethtool.rst36 The application is console-driven using the cmdline DPDK interface:
42 From this interface the available commands and descriptions of what
83 interface that accepts commands as described in `using the
86 defined in the `Ethtool interface`_ to the DPDK functions.
88 Ethtool interface
91 The Ethtool interface is built as a separate library, and implements
/dpdk/doc/guides/prog_guide/
H A Dkernel_nic_interface.rst18 * Allows an interface with the kernel network stack.
32 The KNI kernel loadable module ``rte_kni`` provides the kernel interface
124 in ``struct rte_kni_conf`` when the first KNI interface is created:
158 state of the interface *down* when the interface is management enabled.
161 which require that the carrier state of the KNI interface reflect the
165 the carrier state of the interface to *up* when the interface is management
194 network interface.
207 support callbacks that requires rtnl lock to work (interface down).
270 Called when the management state of the KNI interface changes.
281 Called when the user changes the MAC address of the KNI interface.
[all …]
/dpdk/doc/guides/tools/
H A Ddumpcap.rst9 The interface is similar to the dumpcap tool in Wireshark.
15 from the first available DPDK interface
21 based on interface name and timestamp.
60 Packets received/dropped on interface '0000:00:03.0' 6/0
64 Packets received/dropped on interface '0000:00:03.0' 10/8
78 * ``-t`` -- use a thread per interface.
/dpdk/app/dumpcap/
H A Dmain.c78 struct interface { struct
79 TAILQ_ENTRY(interface) next;
86 TAILQ_HEAD(interface_list, interface); argument
88 static struct interface *port2intf[RTE_MAX_ETHPORTS];
192 struct interface *intf; in add_interface()
422 struct interface *intf; in cleanup_pdump_resources()
474 struct interface *intf; in report_packet_stats()
614 struct interface *intf; in create_output()
673 struct interface *intf; in enable_pdump()

123456