Lines Matching refs:sockets

19 bpf_redirect_map() function. AF_XDP sockets enable the possibility for
116 multiple AF_XDP sockets. To share an UMEM created via one socket A,
135 is a setup with four sockets (all doing TX and RX). Then there will be
244 and monitor the behavior of AF_XDP sockets.
261 This flag enables you to bind multiple sockets to the same UMEM. It
269 sockets bound to the same netdev and queue id. The UMEM (tied to the
278 sockets this way.
281 program. Put all the sockets in the XSK_MAP and just indicate which
320 The second case is when you share a UMEM between sockets that are
323 netdev,queue_id pair. Let us say you want to create two sockets bound
330 socket. These two sockets will now share one and the same UMEM.
333 case where sockets were bound to the same queue id and
336 one queue shared among sockets, so the NIC cannot do this steering. It
342 function for all the sockets you create, or you can use it for the
346 Note that a UMEM can be shared between sockets on the same queue id
409 In libbpf, you can create Rx-only and Tx-only sockets by supplying
459 In order to use AF_XDP sockets two parts are needed. The
539 demonstrates how to use AF_XDP sockets with private UMEMs. Say that
600    to sockets bound to the same queue id X. The XSKMAP can contain
601    sockets bound to different queue ids, for example X and Y, but only
602    traffic goming in from queue id Y can be directed to sockets bound