da5e36308d
Allow multiple listener sockets to bind to the same port. Motivation for soresuseport would be something like a web server binding to port 80 running with multiple threads, where each thread might have it's own listener socket. This could be done as an alternative to other models: 1) have one listener thread which dispatches completed connections to workers. 2) accept on a single listener socket from multiple threads. In case #1 the listener thread can easily become the bottleneck with high connection turn-over rate. In case #2, the proportion of connections accepted per thread tends to be uneven under high connection load (assuming simple event loop: while (1) { accept(); process() }, wakeup does not promote fairness among the sockets. We have seen the disproportion to be as high as 3:1 ratio between thread accepting most connections and the one accepting the fewest. With so_reusport the distribution is uniform. Signed-off-by: Tom Herbert <therbert@google.com> Signed-off-by: David S. Miller <davem@davemloft.net> |
||
---|---|---|
.. | ||
ipv4 | ||
ipv6 | ||
nf_conntrack_acct.h | ||
nf_conntrack_core.h | ||
nf_conntrack_ecache.h | ||
nf_conntrack_expect.h | ||
nf_conntrack_extend.h | ||
nf_conntrack_helper.h | ||
nf_conntrack_l3proto.h | ||
nf_conntrack_l4proto.h | ||
nf_conntrack_timeout.h | ||
nf_conntrack_timestamp.h | ||
nf_conntrack_tuple.h | ||
nf_conntrack_zones.h | ||
nf_conntrack.h | ||
nf_log.h | ||
nf_nat_core.h | ||
nf_nat_helper.h | ||
nf_nat_l3proto.h | ||
nf_nat_l4proto.h | ||
nf_nat.h | ||
nf_queue.h | ||
nf_tproxy_core.h | ||
nfnetlink_log.h | ||
nfnetlink_queue.h | ||
xt_log.h | ||
xt_rateest.h |