| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <200808072009.34891.rdenis@simphalempin.com> Date: Thu, 7 Aug 2008 20:09:34 +0300 From: Rémi Denis-Courmont <rdenis@...phalempin.com> To: "Tom Herbert" <therbert@...gle.com> Cc: netdev@...r.kernel.org Subject: Re: SO_REUSEPORT? Le jeudi 7 août 2008 19:57:15 Tom Herbert, vous avez écrit : > Hello, > > We are looking at ways to scale TCP listeners. I think we like is the > ability to listen on a port from multiple threads (sockets bound to > same port, INADDR_ANY, and no interface binding) , which is what > SO_REUSEPORT would seem to allow. Has this ever been implemented for > Linux or is there a good reason not to have it? On Linux, SO_REUSEADDR provide most of what SO_REUSEPORT provides on BSD. In any case, there is absolutely no point in creating multiple TCP listeners. Multiple threads can accept() on the same listener - at the same time. -- Rémi Denis-Courmont http://www.remlab.net/ -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists