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
197 Busy polling
200 Busy polling allows a user process to check for incoming packets before
201 the device interrupt fires. As is the case with any busy polling it trades
202 off CPU cycles for lower latency (production uses of NAPI busy polling
205 Busy polling is enabled by either setting ``SO_BUSY_POLL`` on
207 ``net.core.busy_read`` sysctls. An io_uring API for NAPI busy polling
213 While busy polling is supposed to be used by low latency applications,
222 polling operation periodically, and the driver should keep the device IRQs
227 The NAPI budget for busy polling is lower than the default (which makes
228 sense given the low latency intention of normal busy polling). This is