The thundering herd issue applies just as much in the kqueue case, if you set it up with N processes all interested in an event on the same socket. Waking them all up is still going to be an O(N) operation.
The "non-broadcast wakeup" solution - ie EPOLLEXCLUSIVE - will also work just as well there.
The "non-broadcast wakeup" solution - ie EPOLLEXCLUSIVE - will also work just as well there.