3 ms·

Meh. SO_REUSEPORT doesn't change the way socket servers are written. I was expecting something, like syscall batching for sockets, but not this.

• rdtsc 13y ago
  They way I understood it, it does change because it simplifies the server. There is no need for one top level listening process/thread. Each separate process/thread can open the listening socket independently. (Btw, there is another interesting forking-for-client-connection pattern in Erlang. Instead of forking off and handling the client connection in a separate process, instead handle the client connection in the accepting process but fork-off another process to continue accepting. In general, just a process pool, that should be easier to set up with this new feature).
  • pfraze 13y ago
    > There is no need for one top level listening process/thread And as a result, the user can configure the prefetch pool.
    • masklinn 13y ago
      And more importantly can easily alter it on the fly (just spawn a new "worker" or kill one)
• RivieraKid 13y ago
  Pretty much, it's just some small unimportant technical detail.