Lines Matching refs:TX

25 TX ring. A socket can receive packets on the RX ring and it can send
26 packets on the TX ring. These rings are registered and sized with the
28 to have at least one of these rings for each socket. An RX or TX
30 UMEM. RX and TX can share the same UMEM so that a packet does not have
31 to be copied between RX and TX. Moreover, if a packet needs to be kept
48 space, for either TX or RX. Thus, the frame addrs appearing in the
50 TX ring. In summary, the RX and FILL rings are used for the RX path
51 and the TX and COMPLETION rings are used for the TX path.
65 process has to create its own socket with associated RX and TX rings,
129 TX. All rings are single-producer/single-consumer, so the user-space
134 with the UMEM must have an RX queue, TX queue or both. Say, that there
135 is a setup with four sockets (all doing TX and RX). Then there will be
136 one FILL ring, one COMPLETION ring, four TX rings and four RX rings.
177 sent (TX ring) and can be used by user-space again.
195 TX Ring
198 The TX ring is used to send frames. The struct xdp_desc descriptor is
263 netdevs/devices. In this mode, each socket has their own RX and TX
273 it in the normal way. Create a second socket and create an RX and a TX
326 and a TX ring, or at least one of them, and then one FILL and
354 present in the FILL ring and the TX ring, the rings for which user
370 If the flag is set for the TX ring, it means that the application
372 TX ring. This can be accomplished either by a poll() call, as in the
377 would look like this for the TX path:
390 syscalls needed for the TX path.
392 XDP_{RX|TX|UMEM_FILL|UMEM_COMPLETION}_RING setsockopts
395 These setsockopts sets the number of descriptors that the RX, TX,
397 to set the size of at least one of the RX and TX rings. If you set
566    allocates one RX and TX queue pair per core. So on a 8 core system,
611    same buffer into the FILL ring and the TX ring at the same time, the