From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Paasch Subject: Re: [RFC 0/2] Delayed binding of UDP sockets for Quic per-connection sockets Date: Wed, 31 Oct 2018 22:07:14 -0700 Message-ID: <3F5491C5-7F64-4325-9D3B-6592F8EDFF33@apple.com> References: <20181031232635.33750-1-cpaasch@apple.com> <0ce864f0-38b9-59cc-18ea-e071afca347d@gmail.com> <20181101035050.GO80792@MacBook-Pro-19.local> <74393778-62e8-76f5-3bfc-ae280b407278@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: netdev@vger.kernel.org, Ian Swett , Leif Hedstrom , Jana Iyengar To: Eric Dumazet Return-path: Received: from ma1-aaemail-dr-lapp03.apple.com ([17.171.2.72]:40588 "EHLO ma1-aaemail-dr-lapp03.apple.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726208AbeKAOIn (ORCPT ); Thu, 1 Nov 2018 10:08:43 -0400 In-reply-to: <74393778-62e8-76f5-3bfc-ae280b407278@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: > On Oct 31, 2018, at 10:04 PM, Eric Dumazet wrote:= >=20 >=20 >=20 >> On 10/31/2018 08:50 PM, Christoph Paasch wrote: >>=20 >> What we had here is that we wanted to let a server initiate more than 64K= >> connections *while* binding also to a source-IP. >> With TCP the bind() would then pick a source-port and we ended up hitting= the >> 64K limit. If we could do an atomic "bind + connect", source-port selecti= on >> could ensure that the 4-tuple is unique. >>=20 >> Or has something changed in recent times that allows to use the 4-tuple >> matching when doing this with TCP? >=20 >=20 > Well, yes, although it is not really recent (this came with linux-4.2) >=20 > You can now bind to an address only, and let the sport being automatically= chosen at connect() Oh, I didn=E2=80=99t knew about this socket option. Thanks :-) Christoph >=20 > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/= ?id=3D90c337da1524863838658078ec34241f45d8394d >=20