[systemd-bugs] [Bug 59912] RFE: Pass a socket to multiple application instances

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=59912

--- Comment #2 from rektide at voodoowarez.com ---
A bit more SO_REUSEPORT in the news-

"On top of that, last year we added a lot more headroom to our future growth by
enabling the marvelous SO_REUSEPORT, a new flag available in Linux 3.9+ that
allows several threads to bind the same port simultaneously instead of having
to race for the same socket, having the kernel round-robin between them."
http://githubengineering.com/brubeck/

"With the SO_REUSEPORT option enabled, there are multiple socket listeners for
each IP address and port combination, one for each worker process. The kernel
determines which available socket listener (and by implication, which worker)
gets the connection. This can reduce lock contention between workers accepting
new connections, and improve performance on multicore systems."
http://nginx.com/blog/socket-sharding-nginx-release-1-9-1/

But I'm starting to think this RFE is incorrect. SO_REUSEPORT is all about
allowing new instances to start independently and bind to the existing port:
it's explicitly about *not* passing the same socket around to a bunch of
children. Alternatively, systemd might be able to do socket-activation with
indepedent so_reuseport 'ed sockets, creating a socket for each
service-instance.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150615/5e28094f/attachment.html>