Lines Matching full:polling

16 interrupts first (:ref:`busy polling<poll>`).
121 the NAPI instance - until NAPI polling finishes any further
155 mapped to queues and interrupts. NAPI is primarily a polling/processing
255 Busy polling
258 Busy polling allows a user process to check for incoming packets before
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
263 Busy polling is enabled by either setting ``SO_BUSY_POLL`` on
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:
311 While busy polling is supposed to be used by low latency applications,
320 polling operation periodically, and the driver should keep the device IRQs
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
342 polling applications may be able to mitigate how much user processing happens
356 while busy polling (for example, because network traffic levels subsided), IRQ
400 IRQ suspension causes the system to alternate between polling mode and
402 overrides ``gro_flush_timeout`` and keeps the system busy polling, but when