Lines Matching full:bind

53 The socket is then finally bound with a bind() call to a device and a
54 specific queue id on that device, and it is not until bind is
59 corresponding two rings, sets the XDP_SHARED_UMEM flag in the bind
112 system call. A UMEM is bound to a netdev and queue id, via the bind()
246 XDP_COPY and XDP_ZERO_COPY bind flags
249 When you bind to a socket, the kernel will first try to use zero-copy
253 pass the XDP_COPY flag to the bind call, the kernel will force the
254 socket into copy mode. If it cannot use copy mode, the bind call will
258 XDP_SHARED_UMEM bind flag
261 This flag enables you to bind multiple sockets to the same UMEM. It
266 unique netdev and queue id tuple that you bind to.
272 we have bound to. To use this mode, create the first socket and bind
275 ones from the first socket will be used. In the bind call, set he
325 and bind it in the normal way. Create a second socket and create an RX
327 COMPLETION ring for this socket. Then in the bind call, set he
350 XDP_USE_NEED_WAKEUP bind flag
355 space is a producer. When this option is set in the bind call, the
568    bind call or the xsk_socket__create libbpf function call, you
569    specify a specific queue id to bind to and it is only the traffic
571    example above, if you bind to queue 0, you are NOT going to get any
579    id 0, and then bind to queue 0. You can use ethtool to do this::
585    that you can bind your XDP socket to. Here is one example in which