You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a way to use mlultiple accepting threads for our "clustering". This will cause MxN communications so we need to rely on #23 for implementing it.
For all the M accepting threads, we want either (a) use the same socket across all the threads, or (b) SO_REUSEPORT (supposedly Linux-only; see http://man7.org/linux/man-pages/man7/socket.7.html for documentation, if proven necessary we may even use SO_ATTACH_REUSEPORT_CBPF / SO_ATTACH_REUSEPORT_EBPF to ensure round-robin behaviour).
In ANY of two cases above, we have to implement one single inter-thread data storage for decision-making on "where we should send accepted socket". Currently suggested way of implementing it:
all the data below is protected by one single mutex
Depends on #23
We need a way to use mlultiple accepting threads for our "clustering". This will cause MxN communications so we need to rely on #23 for implementing it.
For all the M accepting threads, we want either (a) use the same socket across all the threads, or (b) SO_REUSEPORT (supposedly Linux-only; see http://man7.org/linux/man-pages/man7/socket.7.html for documentation, if proven necessary we may even use SO_ATTACH_REUSEPORT_CBPF / SO_ATTACH_REUSEPORT_EBPF to ensure round-robin behaviour).
In ANY of two cases above, we have to implement one single inter-thread data storage for decision-making on "where we should send accepted socket". Currently suggested way of implementing it: