Re: [PATCH] io_uring/napi: drop the single NAPI busy poll special case

[Jens Axboe]

On 10/26/26 5:17 PM, Cinq Prairie wrote:
> I'm thinking that with the re-entry in place io_uring can cond_resched()
> when the napi loop bailed on a need_resched() then resume, between laps
> it holds nothing from the list and is in sleepable context. That would
> mirror the socket path. Though it also impacts the multi-NAPI path,
> which never yielded so far, so I'd like your preference: include it in
> v2, or keep v2 to the single-NAPI fix and send the yield as a follow-up?

Let's keep v2 the single-NAPI fix, and then you can do a follow-up
on top of that.

> I'll also add numbers for the single-NAPI fast path when it is not cut
> short, before/after, so the cost is visible.

Sounds good, thanks!

-- 
Jens Axboe