This is the correct answer (on Linux) and the article dismisses it after lightly touching on it’s correctness.

In a multi-threaded environment someone needs to pay the cost of synchronization if the entire event-queue is loadbalanced. If you don’t want the events to be trivially load-balanced and want the events from one fd to be delivered to a single worker, then it’s way better to use SO_REUSEPORT and get it right from the get go.

Expecting kernel to solve a problem of user-space’s making is asking for trouble - can be done, but the edge cases will sink your project!