| /Documentation/networking/ |
| D | napi.rst | 6 NAPI title
9 NAPI is the event handling mechanism used by the Linux networking stack.
10 The name NAPI no longer stands for anything in particular [#]_.
14 The host then schedules a NAPI instance to process the events.
15 The device may also be polled for events via NAPI without receiving
18 NAPI processing usually happens in the software interrupt context,
20 for NAPI processing.
22 All in all NAPI abstracts away from the drivers the context and configuration
28 The two most important elements of NAPI are the struct napi_struct
30 of the NAPI instance while the method is the driver-specific event
[all …]
|
| D | multi-pf-netdev.rst | 90 The relation between PF, irq, napi, and queue can be observed via netlink spec::
93 [{'id': 0, 'ifindex': 13, 'napi-id': 539, 'type': 'rx'},
94 {'id': 1, 'ifindex': 13, 'napi-id': 540, 'type': 'rx'},
95 {'id': 2, 'ifindex': 13, 'napi-id': 541, 'type': 'rx'},
96 {'id': 3, 'ifindex': 13, 'napi-id': 542, 'type': 'rx'},
97 {'id': 4, 'ifindex': 13, 'napi-id': 543, 'type': 'rx'},
98 {'id': 0, 'ifindex': 13, 'napi-id': 539, 'type': 'tx'},
99 {'id': 1, 'ifindex': 13, 'napi-id': 540, 'type': 'tx'},
100 {'id': 2, 'ifindex': 13, 'napi-id': 541, 'type': 'tx'},
101 {'id': 3, 'ifindex': 13, 'napi-id': 542, 'type': 'tx'},
[all …]
|
| D | page_pool.rst | 54 This lockless guarantee naturally comes from running under a NAPI softirq.
55 The protection doesn't strictly have to be NAPI, any guarantee that allocating
143 pp_params.napi = napi; /* only if locking is tied to NAPI */
155 NAPI poller
161 /* NAPI Rx poller */
|
| D | netdevices.rst | 289 napi->poll:
291 NAPI_STATE_SCHED bit in napi->state. Device
293 all NAPI instances which will do a sleeping poll on the
294 NAPI_STATE_SCHED napi->state bit, waiting for all pending
295 NAPI activity to cease.
|
| D | index.rst | 81 napi
|
| /Documentation/netlink/specs/ |
| D | netdev.yaml | 39 support in the driver napi callback.
139 name: napi-id
140 doc: Id of NAPI using this Page Pool instance.
229 name: napi
233 doc: ifindex of the netdevice to which NAPI instance belongs.
239 doc: ID of the NAPI instance.
243 doc: The associated interrupt vector number for the napi
247 doc: PID of the napi thread, if NAPI is configured to operate in
248 threaded mode. If NAPI is not in threaded mode (i.e. uses normal
272 name: napi-id
[all …]
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | e100.rst | 149 NAPI section in Additional Configurations
152 NAPI (Rx polling mode) is supported in the e100 driver.
154 See :ref:`Documentation/networking/napi.rst <napi>` for more information.
|
| D | i40e.rst | 399 NAPI section in Identifying Your Adapter
401 NAPI (Rx polling mode) is supported in the i40e driver.
403 See :ref:`Documentation/networking/napi.rst <napi>` for more information.
|
| D | ice.rst | 813 NAPI section in Additional Features and Configurations
816 This driver supports NAPI (Rx polling mode).
818 See :ref:`Documentation/networking/napi.rst <napi>` for more information.
|
| D | e1000.rst | 182 RX_POLLING (NAPI) and default driver settings.
|
| /Documentation/translations/zh_CN/mm/ |
| D | page_frags.rst | 30 将禁用中断，而 ”napi“ 前缀的函数只可以在softirq上下文中使用。
|
| /Documentation/networking/device_drivers/can/ctu/ |
| D | ctucanfd-driver.rst | 178 - Submit RX frames to the network subsystem: ISR and NAPI
212 them to SW RX queue. Usually NAPI is used as a middle layer (see ).
214 .. _sec:socketcan:napi:
216 NAPI section in About SocketCAN
224 is NAPI – *the New API*. It is similar to classical top-half/bottom-half
232 See :ref:`Documentation/networking/napi.rst <napi>` for more information.
334 Frame reception is handled in NAPI queue, which is enabled from ISR when
337 has been reached for the NAPI poll run (see ). Each frame is then passed
|
| /Documentation/networking/device_drivers/ethernet/amazon/ |
| D | ena.rst | 187 unmasked by the driver after NAPI processing is complete.
201 updated by the driver dynamically and adjusted every NAPI cycle
297 - The interrupt handler schedules NAPI.
312 - The interrupt handler schedules NAPI.
332 stack, using the NAPI interface function :code:`napi_gro_receive()`.
|
| /Documentation/mm/ |
| D | page_frags.rst | 31 functions will disable interrupts, while the "napi" prefixed functions are
|
| /Documentation/admin-guide/sysctl/ |
| D | net.rst | 135 The maximum number of packets that kernel can handle on a NAPI interrupt,
144 RPS (e.g. RFS, aRFS) processing is competing with the registered NAPI poll function
275 Maximum number of packets taken from all interfaces in one polling cycle (NAPI
284 Maximum number of microseconds in one NAPI polling cycle. Polling
410 GRO has decided not to coalesce, it is placed on a per-NAPI list. This
|
| /Documentation/bpf/ |
| D | bpf_prog_run.rst | 93 maximum NAPI receive batch size), but can be specified by userspace through
|
| /Documentation/networking/device_drivers/ethernet/neterion/ |
| D | s2io.rst | 179 d. Enable NAPI feature(in kernel configuration Device Drivers ---> Network
|
| /Documentation/networking/device_drivers/ethernet/stmicro/ |
| D | stmmac.rst | 207 This is based on NAPI, so the interrupt handler signals only if there is work
217 The driver is able to mitigate the number of its DMA interrupts using NAPI for
400 15) Force to disable the RX Watchdog feature and switch to NAPI mode::
|
| /Documentation/networking/device_drivers/ethernet/google/ |
| D | gve.rst | 117 The handler for these irqs schedule the napi for that block to run
|
| /Documentation/networking/device_drivers/ethernet/aquantia/ |
| D | atlantic.rst | 63 NAPI section in Configuration
65 NAPI (Rx polling mode) is supported in the atlantic driver.
|
| /Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| D | counters.rst | 408 - The number of invocations of NAPI poll of channel i.
412 - The number of times the NAPI poll function completed and armed the
417 - The number of times the NAPI poll function explicitly stopped execution
430 - Number of times NAPI is triggered by XSK wakeups by posting a NOP to
|
| /Documentation/networking/devlink/ |
| D | mlx5.rst | 177 in napi context via triggering an irq. In case of a failure to get
|
| /Documentation/RCU/ |
| D | checklist.rst | 266 network-driver NAPI (softirq) context. BPF relies heavily on RCU
269 section in a NAPI poll cycle, this usage is safe. The reason
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net | 347 set this value to enable/disable threaded mode for all napi
|
| /Documentation/networking/device_drivers/ethernet/altera/ |
| D | altera_tse.rst | 102 using NAPI for receive operations. Interrupt mitigation is not yet supported
|