Lines Matching full:busy

16 interrupts first (:ref:`busy polling<poll>`).
224 Busy polling
227 Busy polling allows a user process to check for incoming packets before
228 the device interrupt fires. As is the case with any busy polling it trades
229 off CPU cycles for lower latency (production uses of NAPI busy polling
232 Busy polling is enabled by either setting ``SO_BUSY_POLL`` on
234 ``net.core.busy_read`` sysctls. An io_uring API for NAPI busy polling
237 epoll-based busy polling
255 In order to enable busy polling, there are two choices:
257 1. ``/proc/sys/net/core/busy_poll`` can be set with a time in useconds to busy
259    epoll-based applications to busy poll when they call epoll_wait. This may
260    not be desirable as many applications may not have the need to busy poll.
280 While busy polling is supposed to be used by low latency applications,
288 Such applications can pledge to the kernel that they will perform a busy
292 if ``gro_flush_timeout`` passes without any busy poll call. For epoll-based
293 busy polling applications, the ``prefer_busy_poll`` field of ``struct
297 The NAPI budget for busy polling is lower than the default (which makes
298 sense given the low latency intention of normal busy polling). This is
300 with the ``SO_BUSY_POLL_BUDGET`` socket option. For epoll-based busy polling
309 attempting to busy poll by device IRQs and softirq processing. This value
310 should be chosen carefully with these tradeoffs in mind. epoll-based busy
325 while busy polling (for example, because network traffic levels subsided), IRQ
345      to defer IRQs after busy poll has found no data.
370 irq-driven packet delivery. During busy periods, ``irq-suspend-timeout``
371 overrides ``gro_flush_timeout`` and keeps the system busy polling, but when
380 3) epoll -> busy-poll -> napi poll; busy looping
388 During busy periods, ``irq-suspend-timeout`` is used as timer in Loop 2,