Lines Matching +full:wait +full:- +full:queue
1 .. SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
30 of the NAPI instance while the method is the driver-specific event
37 -----------
55 ------------
64 argument - drivers can process completions for any number of Tx
95 not call napi_complete_done() and wait to be called again,
96 or return ``budget - 1``.
101 -------------
109 As mentioned in the :ref:`drv_ctrl` section - napi_disable() and subsequent
110 calls to the poll method only wait for the ownership of the instance
118 --------------------------
121 the NAPI instance - until NAPI polling finishes any further
125 to IRQ being auto-masked by the device) should use the napi_schedule_prep()
128 .. code-block:: c
130 if (napi_schedule_prep(&v->napi)) {
131 mydrv_mask_rxtx_irq(v->idx);
133 __napi_schedule(&v->napi);
138 .. code-block:: c
140 if (budget && napi_complete_done(&v->napi, work_done)) {
141 mydrv_unmask_rxtx_irq(v->idx);
142 return min(work_done, budget - 1);
150 Instance to queue mapping
151 -------------------------
156 abstraction without specific user-facing semantics. That said, most networking
159 NAPI instances most often correspond 1:1:1 to interrupts and queue pairs
160 (queue pair is a set of a single Rx and single Tx queue).
164 core. Regardless of the queue assignment, however, there is usually still
182 -----------------------
198 ------------
211 ---------------
216 Very high request-per-second applications (especially routing/forwarding
235 -------------
241 thread (called ``napi/${ifc-name}-${napi-id}``).