Documentation/networking/af_xdp.rst

24 syscall. Associated with each XSK are two rings: the RX ring and the
25 TX ring. A socket can receive packets on the RX ring and it can send
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
44 to fill in with RX packet data. References to these frames will then
45 appear in the RX ring once each packet has been received. The
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
62 then receive frame addr references in its own RX ring that point to
65 process has to create its own socket with associated RX and TX rings,
128 There are a four different kind of rings: FILL, COMPLETION, RX and
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.
159 Frames passed to the kernel are used for the ingress path (RX rings).
182 RX Ring
185 The RX ring is the receiving side of a socket. Each entry in the ring
190 descriptors will (or can) appear on the RX ring.
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
325 and bind it in the normal way. Create a second socket and create an RX
361 poll() to be able to continue to receive packets on the RX ring. This
363 more buffers on the FILL ring and no buffers left on the RX HW ring of
373 RX path, or by calling sendto().
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,