On Thu, 11 Jun 2026 15:12:40 +0800 [email protected] wrote: > For now, we use sk_busy_loop() for both rx and tx path. The sk_busy_loop() > will call napi_busy_loop() for the specified napi_id. However, some > nic drivers have tx napi, such as virtio-net. In this case, sk_busy_loop() > doesn't work, as it can only schedule the NAPI for the rx queue. > > Therefore, introduce sk_tx_busy_loop() for the nic drivers that support tx > napi, which will schedule the tx napi if available.
First, I thought the only difference with Tx NAPI is that it can't be busy polled. So if you want to poll an instance don't register it as a Tx one instead of adding all this "tx polling" stuff in the core? Second, can this problem happen for any other NIC or is it purely an artifact of virtio's delayed Tx completion handling? Third, this series does not apply.
