Lines Matching refs:flag

59 corresponding two rings, sets the XDP_SHARED_UMEM flag in the bind
117 the next socket B can do this by setting the XDP_SHARED_UMEM flag in
253 pass the XDP_COPY flag to the bind call, the kernel will force the
255 fail with an error. Conversely, the XDP_ZEROCOPY flag will force the
258 XDP_SHARED_UMEM bind flag
261 This flag enables you to bind multiple sockets to the same UMEM. It
350 XDP_USE_NEED_WAKEUP bind flag
353 This option adds support for a new flag called need_wakeup that is
356 need_wakeup flag will be set if the kernel needs to be explicitly
357 woken up by a syscall to continue processing packets. If the flag is
360 If the flag is set on the FILL ring, the application needs to call
366 need_wakeup flag is set so that user space can put buffers on the
370 If the flag is set for the TX ring, it means that the application
375 An example of how to use this flag can be found in
384 I.e., only use the syscall if the flag is set.
402 socket. But if the XDP_SHARED_UMEM flag is used, any socket after the
434 be dealt with in separate sections for each UMEM flag.
484 flag XDP_USE_SG. If this is not provided, all multi-buffer packets
489 To represent a packet consisting of multiple frames, a new flag called
493 of the packet. Why the reverse logic of end-of-packet (eop) flag found
528 multiple descriptors, if needed, and sets the XDP_PKT_CONTD flag as
531 flag set to one, it means that the packet consists of multiple buffers
723 query for NETDEV_XDP_ACT_RX_SG support. This is the same flag as for
729 flag. If it is set, it means that at least zero-copy is supported and
834    XDP_SHARED_UMEM flag.