Conversation

They've been using EPOLLEXCLUSIVE since shortly after it became available. It replaced needing accept_mutex to avoid unnecessary wakeups. Linux could have used round-robin load balancing for EPOLLEXCLUSIVE as they do for REUSEPORT instead of pathological behavior being standard.
Replying to
REUSEPORT isn't a strict upgrade over EPOLLEXCLUSIVE. It distributes the connections (TCP) / messages (UDP) via round-robin without needing synchronization across them. EPOLLEXCLUSIVE avoids giving work to a worker that's currently not waiting but isn't as ridiculously scalable.
1
3
It would help if nginx finally got upstream support for async open. REUSEPORT will work increasingly well as the remaining blocking goes away. They still don't use io_uring but mostly because thread pool AIO works well enough that io_uring would mostly just reduce CPU use a bit.
4