soreuseport: TCP/IPv6 implementation
Motivation for soreuseport 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>
Showing
- include/net/inet6_hashtables.h 4 additions, 1 deletioninclude/net/inet6_hashtables.h
- include/net/netfilter/nf_tproxy_core.h 1 addition, 0 deletionsinclude/net/netfilter/nf_tproxy_core.h
- net/ipv6/inet6_connection_sock.c 14 additions, 5 deletionsnet/ipv6/inet6_connection_sock.c
- net/ipv6/inet6_hashtables.c 16 additions, 3 deletionsnet/ipv6/inet6_hashtables.c
- net/ipv6/tcp_ipv6.c 3 additions, 1 deletionnet/ipv6/tcp_ipv6.c
Please register or sign in to comment