Florian Fainelli <f.faine...@gmail.com> : [...] > Typically, NAPI is used at the receive side of the Ethernet NIC/driver > to lower the hard/soft interrupt context switch, although there is > nothing that prevent you to implement a similar scheme for the > transmit side. Usually, for transmit you will be submitting one packet > for transmission and get a completion interrupt, so without interrupt > coalescing (software or hardware) you can end-up with 1 interrupt per > packet transmitted.
The wording is a bit shy: there is a long standing policy to move everything to NAPI context (as well as go mostly lockless, etc.). Any taker to move macb Tx processing to NAPI context or should I consider it ? -- Ueimor -- To unsubscribe from this list: send the line "unsubscribe netdev" in
