Lines Matching refs:busy

16 interrupts first (:ref:`busy polling<poll>`).
259 the device interrupt fires. As is the case with any busy polling it trades
260 off CPU cycles for lower latency (production uses of NAPI busy polling
265 ``net.core.busy_read`` sysctls. An io_uring API for NAPI busy polling
268 epoll-based busy polling
286 In order to enable busy polling, there are two choices:
288 1. ``/proc/sys/net/core/busy_poll`` can be set with a time in useconds to busy
290    epoll-based applications to busy poll when they call epoll_wait. This may
291    not be desirable as many applications may not have the need to busy poll.
311 While busy polling is supposed to be used by low latency applications,
319 Such applications can pledge to the kernel that they will perform a busy
323 if ``gro_flush_timeout`` passes without any busy poll call. For epoll-based
324 busy polling applications, the ``prefer_busy_poll`` field of ``struct
328 The NAPI budget for busy polling is lower than the default (which makes
329 sense given the low latency intention of normal busy polling). This is
331 with the ``SO_BUSY_POLL_BUDGET`` socket option. For epoll-based busy polling
340 attempting to busy poll by device IRQs and softirq processing. This value
341 should be chosen carefully with these tradeoffs in mind. epoll-based busy
356 while busy polling (for example, because network traffic levels subsided), IRQ
376      to defer IRQs after busy poll has found no data.
401 irq-driven packet delivery. During busy periods, ``irq-suspend-timeout``
402 overrides ``gro_flush_timeout`` and keeps the system busy polling, but when
411 3) epoll -> busy-poll -> napi poll; busy looping
419 During busy periods, ``irq-suspend-timeout`` is used as timer in Loop 2,