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
266 also exists. Threaded polling of NAPI also has a mode to busy poll for
267 packets (:ref:`threaded busy polling<threaded_busy_poll>`) using the NAPI
270 epoll-based busy polling
288 In order to enable busy polling, there are two choices:
313 While busy polling is supposed to be used by low latency applications,
322 polling operation periodically, and the driver should keep the device IRQs
326 busy polling applications, the ``prefer_busy_poll`` field of ``struct
330 The NAPI budget for busy polling is lower than the default (which makes
331 sense given the low latency intention of normal busy polling). This is
333 with the ``SO_BUSY_POLL_BUDGET`` socket option. For epoll-based busy polling
344 polling applications may be able to mitigate how much user processing happens
358 while busy polling (for example, because network traffic levels subsided), IRQ
402 IRQ suspension causes the system to alternate between polling mode and
404 overrides ``gro_flush_timeout`` and keeps the system busy polling, but when
433 Threaded NAPI busy polling
436 Threaded NAPI busy polling extends threaded NAPI and adds support to do
437 continuous busy polling of the NAPI. This can be useful for forwarding or
440 Threaded NAPI busy polling can be enabled on per NIC queue basis using Netlink.
455 Once threaded busy polling is enabled for a NAPI, PID of the kthread can be
465 kthread that is polling this NAPI.