Lines Matching full:polling

16 interrupts first (:ref:`busy polling<poll>`).
121 the NAPI instance - until NAPI polling finishes any further
156 mapped to queues and interrupts. NAPI is primarily a polling/processing
198 Busy polling
201 Busy polling allows a user process to check for incoming packets before
202 the device interrupt fires. As is the case with any busy polling it trades
203 off CPU cycles for lower latency (production uses of NAPI busy polling
206 Busy polling is enabled by either setting ``SO_BUSY_POLL`` on
208 ``net.core.busy_read`` sysctls. An io_uring API for NAPI busy polling
214 While busy polling is supposed to be used by low latency applications,
223 polling operation periodically, and the driver should keep the device IRQs
228 The NAPI budget for busy polling is lower than the default (which makes
229 sense given the low latency intention of normal busy polling). This is