At Fastly, we have SO_REUSEPORT and :80 as an address, 16 times :) On Wed, Mar 18, 2015 at 4:50 PM Federico Schwindt <[email protected]> wrote:
> My understanding and what I've read is that if you have multiple threads > accepting connections it'll will behave much better when running in > multiple cores which is pretty much everyone these days. > > Now looking at master, it looks we only have one acceptor per address and > not per pools. > > Am I not reading the code correctly, has this changed since 4.0 or it's > always been one acceptor per address? > > > > On Wed, Mar 18, 2015 at 10:49 AM, Poul-Henning Kamp <[email protected]> > wrote: > >> -------- >> In message < >> cajv_h0awhzhjbq2u5o24fwqfknmnv73qhgw2f4r0-sxpjdq...@mail.gmail.com> >> , Federico Schwindt writes: >> >> >Is it time to consider SO_REUSEPORT in Linux? >> >> I have no idea... In what context and what would it do ? >> >> -- >> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 >> [email protected] | TCP/IP since RFC 956 >> FreeBSD committer | BSD since 4.3-tahoe >> Never attribute to malice what can adequately be explained by >> incompetence. >> > > _______________________________________________ > varnish-dev mailing list > [email protected] > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
_______________________________________________ varnish-dev mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
