| /dpdk/examples/pipeline/examples/ |
| H A D | l2fwd_macswp.spec | 13 header ethernet instanceof ethernet_h 29 mov m.addr h.ethernet.dst_addr 30 mov h.ethernet.dst_addr h.ethernet.src_addr 31 mov h.ethernet.src_addr m.addr 54 extract h.ethernet 57 emit h.ethernet
|
| H A D | fib.spec | 48 header ethernet instanceof ethernet_h 86 mov h.ethernet.dst_addr t.ethernet_dst_addr 87 mov h.ethernet.src_addr t.ethernet_src_addr 88 mov h.ethernet.ethertype t.ethernet_ethertype 89 validate h.ethernet 161 extract h.ethernet 168 emit h.ethernet
|
| H A D | registers.spec | 34 header ethernet instanceof ethernet_h 58 extract h.ethernet 64 emit h.ethernet
|
| H A D | meter.spec | 34 header ethernet instanceof ethernet_h 57 extract h.ethernet 60 emit h.ethernet
|
| H A D | selector.spec | 51 header ethernet instanceof ethernet_h 88 extract h.ethernet 90 mov m.group_id h.ethernet.dst_addr 92 emit h.ethernet
|
| H A D | varbit.spec | 47 header ethernet instanceof ethernet_h 69 extract h.ethernet 90 emit h.ethernet
|
| H A D | vxlan.spec | 40 header ethernet instanceof ethernet_h 174 h.ethernet.dst_addr exact 191 extract h.ethernet 198 emit h.ethernet
|
| H A D | learner.spec | 41 header ethernet instanceof ethernet_h 121 extract h.ethernet 124 emit h.ethernet
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | bbdev_app.rst | 18 A packet is received on an ethernet port -> enqueued for downlink baseband 22 the ethernet port. 29 * Only one baseband device and one ethernet port can be used. 55 * ``p ETH_PORT_ID``: ethernet port ID (default = 0) 75 device gets linked to a corresponding ethernet port as allowed by 94 This can be done by using DPDK Pktgen to burst traffic on two ethernet ports, and 96 Executing the command below will generate traffic on the two allowed ethernet
|
| H A D | ipsec_secgw.rst | 30 (Look aside crypto accelerator or using ethernet device). It also support 31 inline ipsec processing by the supported ethernet device during transmission. 89 Event mode also supports event vectorization. The event devices, ethernet device 240 * ``--mtu MTU``: MTU value (in bytes) on all attached ethernet ports. 683 accelerator or protocol offload on ethernet device or inline 684 crypto processing on the ethernet device during transmission. 691 * *inline-protocol-offload*: inline protocol offload on ethernet device 692 * *inline-crypto-offload*: inline crypto processing on ethernet device 697 * Port/device ID of the ethernet/crypto accelerator for which the SA is 974 * The destination ethernet address to use for that port [all …]
|
| H A D | l3_forward.rst | 105 * ``--eth-dest=X,MM:MM:MM:MM:MM:MM:`` Optional, ethernet destination for port X. 123 * ``--event-eth-rxqs:`` Optional, Number of ethernet RX queues per device. Only valid if --mode=eve… 209 In case of eventdev mode, *--config* option is not used for ethernet port 210 configuration. Instead each ethernet port will be configured with mentioned
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | event_ethernet_tx_adapter.rst | 11 between the ethernet, crypto and timer devices and the event device. Event adapter 13 The Event ethernet Tx adapter provides configuration and data path APIs for the 127 capability for a given ethernet device, the application should use the 130 If the adapter uses a service function for the ethernet device then the application 171 The event device, ethernet device pairs which support the capability 174 mbufs are destined to the same ethernet port and queue by setting the bit 178 into each mbuf and transmit them to the requested ethernet port and queue pair.
|
| H A D | event_ethernet_rx_adapter.rst | 183 The service core function is typically set up to poll ethernet Rx queues for 190 has to enable Rx queue interrupts when configuring the ethernet device 209 capabilities flags for a particular ethernet device, the service function 212 dequeuing packets from the ethernet device. The application may want to 224 The event devices, ethernet device pairs which support the capability 232 The Rx adapter additionally might include useful data such as ethernet device 269 capabilities flags for a particular ethernet device, the service function 273 and 8-bits of ethernet device identifier.
|
| H A D | rte_security.rst | 21 crypto device and/or ethernet device. 354 The device (crypto or ethernet) capabilities which support security operations, 364 Each driver (crypto or ethernet) defines its own private array of capabilities 523 Discovering the features and capabilities of a driver (crypto/ethernet) 544 The Security framework provides APIs to create and free sessions for crypto/ethernet 554 is used to allocate and initialize a session for the required crypto/ethernet device. 556 Session APIs need a parameter ``rte_security_ctx`` to identify the crypto/ethernet 559 (for ethernet port).
|
| H A D | rawdev.rst | 10 In terms of device flavor (type) support, DPDK currently has ethernet
|
| /dpdk/doc/guides/eventdevs/ |
| H A D | cnxk.rst | 44 - N:1 ethernet device Rx queue to Event queue mapping. 107 Force Rx back pressure when same mempool is used across ethernet device 206 Using the same mempool for all the ethernet device ports connected to 208 ethernet device. 210 ethernet devices connected to event device to override this applications can 212 Using unique mempool per each ethernet device is recommended when they are
|
| /dpdk/doc/guides/nics/ |
| H A D | pfe.rst | 76 module, the PFE HIF driver and the PFE ethernet driver combined represent 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 130 4. The ethernet device will be registered as virtual device, so pfe has dependency on
|
| H A D | dpaa.rst | 50 enqueue and dequeue ethernet frames, thus providing the infrastructure for 124 - Creating necessary ethernet instance before passing control to the PMD 315 …<https://source.codeaurora.org/external/qoriq/qoriq-components/linux/tree/drivers/net/ethernet/fre…
|
| H A D | igc.rst | 11 …<https://ark.intel.com/content/www/us/en/ark/products/series/184686/intel-ethernet-controller-i225…
|
| H A D | enetfec.rst | 46 | | virtual ethernet device | |
|
| H A D | cnxk.rst | 176 pre_l2 headers are custom headers placed before the ethernet header. For 439 CN10K HW provides a misc device Inline device that supports ethernet devices in 442 - Aggregate all the inline IPsec inbound traffic from all the CN10K ethernet
|
| /dpdk/doc/guides/tools/ |
| H A D | testeventdev.rst | 113 Use ethernet device as producer. 178 Configure multiple Rx queues per each ethernet port. 198 Configure unique mempool per ethernet device, the size of each pool 408 uses the probed ethernet devices as producers by configuring them as Rx 460 Example command to run perf queue test with ethernet ports: 576 #. Measure the end-to-end performance of an event dev with a ethernet dev. 594 | | | | the number of detected ethernet devices.| 626 The number of producers depends on the number of ethernet devices detected and 627 each ethernet device is configured as a event_eth_rx_adapter that acts as a 700 #. Measure the end-to-end performance of an event dev with a ethernet dev. [all …]
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | bcmfs.rst | 10 <https://www.broadcom.com/products/ethernet-connectivity/network-adapters/smartnic>`__. 59 `Broadcom Official Website <https://www.broadcom.com/products/ethernet-connectivity
|
| /dpdk/drivers/net/dpaa/ |
| H A D | dpaa_rxtx.h | 169 uint16_t ethernet:1; member 188 uint16_t ethernet:1;
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_17_11.rst | 164 for protocols like IPsec using inline ipsec offload to ethernet devices or 175 * **Updated the IXGBE ethernet driver to support rte_security.** 177 Updated ixgbe ethernet PMD to support ``rte_security`` inline IPsec offload. 185 * **Added the i40e ethernet driver to support queue region feature.** 212 Added support for the eventdev ethernet adapter for DPAA2.
|