Searched refs:RX (Results 1 – 25 of 114) sorted by relevance
12345
6 pipeline RX period 10 offset_port_id 07 pipeline RX port in bsz 32 link LINK rxq 08 pipeline RX port out bsz 32 swq RXQ09 pipeline RX table match stub10 pipeline RX port in 0 table 011 pipeline RX table 0 rule add match default action fwd port 020 thread 1 pipeline RX enable
145 pipeline RX table match stub146 pipeline RX port in 0 table 0154 thread 2 pipeline RX enable174 RX queue: 0175 RX desc=512 - RX free threshold=32177 RX Offloads=0x0184 RX queue: 0185 RX desc=0 - RX free threshold=0187 RX Offloads=0x0345 pipeline RX port in 0 table 0[all …]
130 RX packets 0 bytes 0 (0.0 B)131 RX errors 0 dropped 0 overruns 0 frame 0137 RX packets 0 bytes 0 (0.0 B)138 RX errors 0 dropped 0 overruns 0 frame 0158 RX-packets: 35637905 RX-dropped: 0 RX-total: 35637905163 RX-packets: 35637915 RX-dropped: 0 RX-total: 35637915168 RX-packets: 71275820 RX-dropped: 0 RX-total: 71275820
34 There is no change to the PMD API. The RX/TX handlers are the only two entries for35 vPMD packet I/O. They are transparently registered at runtime RX/TX execution39 packet transfers. The following sections explain RX and TX constraints in the43 RX Constraints50 For Vector RX it is assumed that the number of descriptor rings will be a power52 head after hitting the tail without a conditional check. In addition Vector RX56 Features not Supported by Vector RX PMD68 * RX checksum offload90 RX Burst Size94 that the RX burst should be greater than 4 packets per burst. It returns zero if using
107 - Use the RX PCAP file to infinitely receive packets187 One of the first things that testpmd does before starting to forward packets is to flush the RX str…188 by reading the first 512 packets on every RX stream and discarding them.202 Otherwise, the first 512 packets from the input pcap file will be discarded by the RX flushing oper…241 RX queues=1 - RX desc=128 - RX free threshold=0242 RX threshold registers: pthresh=8 hthresh=8 wthresh=4256 RX-packets: 462384736 RX-dropped: 0 RX-total: 462384736
16 There is no change to PMD API. The RX/TX handler are the only two entries for vPMD packet I/O.17 They are transparently registered at runtime RX/TX execution if all condition checks pass.22 The following sections explain RX and TX constraints in the vPMD.24 RX Constraints32 * To enable vPMD to work for RX, bulk allocation for Rx must be allowed.48 vPMD for RX would be disabled.70 Feature not Supported by RX Vector PMD82 * RX checksum off load129 RX Burst Size132 As vPMD is focused on high throughput, it assumes that the RX burst size is equal to or greater tha…[all …]
123 PMD: Available DMA queues RX: 8 TX: 8135 RX queues=2 - RX desc=128 - RX free threshold=0136 RX threshold registers: pthresh=0 hthresh=0 wthresh=0
41 - RX flow control63 - RX queue start/stop is not supported.176 - ``rx_bytes``: number of RX bytes177 - ``rx_packets``: number of RX packets178 - ``rx_unicast_packets``: number of RX unicast packets179 - ``rx_errors``: number of RX MAC errors180 - ``rx_fullq_dropped``: number of RX packets dropped due to full RX queue182 - ``rx_early_dropped``: number of RX packets that were early dropped183 - ``rx_fifo_dropped``: number of RX packets dropped due to RX fifo overrun184 - ``rx_cls_dropped``: number of RX packets dropped by classifier[all …]
18 - Multiple queues for TX and RX34 - Interrupt mode for RX35 - Scattered and gather for TX and RX239 Vector RX Pre-conditions626 16 Byte RX Descriptor setting on DPDK VF629 Currently the VF's RX descriptor mode is decided by PF. There's no PF-VF631 VF its own RX descriptor mode.641 The same rule for DPDK PF + DPDK VF. The PF and VF should use the same RX642 descriptor mode. Or the VF RX will not work.657 RX/TX statistics may be incorrect when register overflowed[all …]
38 * ``-r1``: core mask 0x1 for RX122 worker 12 thread done. RX=4966581 TX=4966581123 worker 13 thread done. RX=4963329 TX=4963329124 worker 14 thread done. RX=4953614 TX=4953614125 worker 0 thread done. RX=0 TX=0126 worker 11 thread done. RX=4970549 TX=4970549127 worker 10 thread done. RX=4986391 TX=4986391128 worker 9 thread done. RX=4970528 TX=4970528129 worker 15 thread done. RX=4974087 TX=4974087130 worker 8 thread done. RX=4979908 TX=4979908[all …]
4 RX/TX Callbacks Sample Application7 The RX/TX Callbacks sample application is a packet forwarding application that18 on top of the latency since the packet was received and processed by the RX53 The sections below explain the additional RX/TX callback code.81 The RX and TX callbacks are added to the ports/queues as function pointers:85 :start-after: RX and TX callbacks are added to the ports. 8<86 :end-before: >8 End of RX and TX callbacks.99 The ``add_timestamps()`` callback is added to the RX port and is applied to104 :start-after: Callback added to the RX port and applied to packets. 8<
23 The RX thread reads packets from the RX port,64 * --pfc "RX PORT, TX PORT, RX LCORE, WT LCORE, TX CORE": Packet flow configuration.78 * A = Size (in number of buffer descriptors) of each of the NIC RX rings read79 by the I/O RX lcores (the default value is 128).82 by the I/O RX lcores to send packets to worker lcores (the default value is 8192).89 * A = I/O RX lcore read burst size from the NIC RX (the default value is 64)91 * B = I/O RX lcore write burst size to the output software rings,100 * --rth "A, B, C": The RX queue threshold parameters102 * A = RX prefetch threshold (the default value is 8)104 * B = RX host threshold (the default value is 8)[all …]
95 The next step is to configure the RX and TX queues.96 For each port, there is only one RX queue (only one lcore is able to poll a given port).102 :start-after: Configure RX and TX queues. 8<103 :end-before: >8 End of configure RX and TX queues.151 RX Queue Initialization163 :start-after: RX queue initialization. 8<164 :end-before: >8 End of RX queue initialization.177 The global configuration for the RX queues is stored in a static structure:212 In the lsi_main_loop() function, the main task is to read ingress packets from the RX queues.217 :start-after: Read packet from RX queues. 8<[all …]
115 To run the application in linux environment with 4 lcores, 16 ports and 8 RX queues per lcore and M…122 To run the application in linux environment with 4 lcores, 4 ports, 8 RX queues123 per lcore, to forward RX traffic of ports 0 & 1 on ports 2 & 3 respectively and204 The next step is to configure the RX and TX queues.205 For each port, there is only one RX queue (only one lcore is able to poll a given port).217 RX Queue Initialization229 :start-after: RX queue setup. 8<230 :end-before: >8 End of RX queue setup.261 In the l2fwd_main_loop() function, the main task is to read ingress packets from the RX queues.266 :start-after: Read packet from RX queues. 8<[all …]
94 To run the application in linux environment with 4 lcores, 16 ports, 8 RX queues per lcore and170 The next step is to configure the RX and TX queues.171 For each port, there is only one RX queue (only one lcore is able to poll a given port).177 :start-after: Configure the RX and TX queues. 8<178 :end-before: >8 End of configuring the RX and TX queues.181 RX Queue Initialization193 :start-after: RX queue initialization. 8<194 :end-before: >8 End of RX queue initialization.238 * Statistics per RX port252 * MAX_PKT_BURST as desired target value (RX burst size)[all …]
51 * -q NQ: Number of RX queues per lcore60 To run the example in linux environment with 2 lcores (2,4) over 2 ports(0,2) with 1 RX queue per l…91 To run the example in linux environment with 1 lcore (4) over 2 ports(0,2) with 2 RX queues per lco…136 To avoid lock contention, each RX queue has its own Fragment Table,137 …andle the situation when different fragments of the same packet arrive through different RX queues.152 To keep mempool size under reasonable limits and to avoid situation when one RX queue can starve ot…153 each RX queue uses its own mempool.207 For all of these signals, the ip_reassembly process prints Fragment table statistics for each RX qu…
111 For this example the ports are set up with 1 RX and 1 TX queue using the123 Finally the RX port is set in promiscuous mode:127 :start-after: Enable RX in promiscuous mode for the Ethernet device.128 :end-before: End of setting RX port in promiscuous mode.152 Packets are received in bursts on the RX ports and transmitted in bursts on
73 * :doc:`RX/TX callbacks Application<rxtx_callbacks>`: The RX/TX76 packets. The application calculates the latency of a packet between RX77 (packet arrival) and TX (packet transmission) by adding callbacks to the RX
193 The next step is to configure the RX and TX queues. For each port, there is only194 one RX queue (only one lcore is able to poll a given port). The number of TX200 :start-after: Configure RX and TX queue. 8<201 :end-before: >8 End of configuration RX and TX queue.204 RX Queue Initialization337 :start-after: Gets service ID for RX/TX adapters. 8<338 :end-before: >8 End of get service ID for RX/TX adapters.347 the RX queues. This is done using the following code:360 function. The processing is very simple: process the TX port from the RX port,381 arriving on the same RX port. Therefore, it would have been possible to call[all …]
61 RX Port and associated core :numref:`dtg_rx_rate`.67 RX packet rate compared against received rate.69 #. Is the configuration for the RX setup correctly?84 * If ``rte_eth_dev_stats`` shows drops are on specific RX queues, ensure RX99 * If there are multiple port queue pair, it might be the RX thread, RX100 distributor, or event RX adapter not having enough cycles.102 * If there are drops seen for RX adapter or RX distributor, try using110 RX-TX port and associated cores :numref:`dtg_rx_tx_drop`.116 RX-TX drops118 #. At RX[all …]
5 ; Each NIC splits the input traffic into 4 RX queues, with each of its RX queues17 ; | RX |---------+ | | | |24 ; | RX |-------|-|-------+ | | | | +-----------+ +----------+31 ; | RX |-----+ | +-----|-|---------|-|----->| | | |38 ; | RX |---|---|-------|---------------+
95 Enable NUMA-aware allocation of RX/TX rings and of RX memory buffers100 Disable NUMA-aware allocation of RX/TX rings and of RX memory buffers (mbufs).109 Where flag is 1 for RX, 2 for TX, and 3 for RX and TX.199 Enable hardware RX checksum offload.203 Enable scatter (multi-segment) RX.278 Set the number of descriptors in the RX rings to N, where N > 0.296 RX hairpin is binded to the first TX hairpin, the second RX hairpin is298 RX hairpin queue is the number of RX queues as configured using --rxq.333 Set the host threshold register of RX rings to N, where N >= 0.469 Set the hexadecimal bitmask of RX queue offloads.[all …]
69 * In UIO, the RX interrupt shares the same vector with other72 * RX interrupt is only implemented for the linux target.128 * Support for RSS and Flow Director hashes in vector RX.270 * Improved performance for both RX and TX operations.352 * **Optimized KNI RX burst size computation.**575 * **fm10k: Fix RX buffer size.**652 * **i40evf: Fix RSS with less RX queues than TX queues.**745 * **ixgbe: Fix RX with buffer address not word aligned.**751 * **ixgbe: Fix RX with buffer address not word aligned.**826 * **ixgbevf: Fix RX function selection.**[all …]
54 * **Added API in ethdev to retrieve RX/TX queue information.**58 RX/TX descriptors min/max/align numbers, per queue, for the device.73 * Added defaults for i210 RX/TX PBSIZE79 * **Added e1000 RX interrupt support.**108 * **Added i40e vector RX/TX.**110 * **Added i40e RX interrupt support.**126 * **Added fm10k vector RX/TX.**169 * Vector RX204 * Added check on RX queues and TX queues of each link355 * **ixgbe: Removed burst size restriction of vector RX.**[all …]
39 enum enetc_bdr_type {TX, RX}; enumerator183 #define enetc_rxbdr_rd(hw, n, off) enetc_bdr_rd(hw, RX, n, off)187 enetc_bdr_wr(hw, RX, n, off, val)