On Mon, Jan 23, 2017 at 01:28:53PM -0800, Wei Wang wrote: > Hi Willy, > > True. If you call connect() multiple times on a socket which already has > cookie without a write(), the second and onward connect() call will return > EINPROGRESS. > It is basically because the following code block in __inet_stream_connect() > can't distinguish if it is the first time connect() is called or not: > > case SS_CONNECTING: > if (inet_sk(sk)->defer_connect) <----- defer_connect will > be 0 only after a write() is called > err = -EINPROGRESS; > else > err = -EALREADY; > /* Fall out of switch with err, set for this state */ > break;
Ah OK that totally makes sense, thanks for the explanation! > I guess we can add some extra logic here to address this issue. So the > second connect() and onwards will return EALREADY. If that's possible at little cost it would be nice, because your patch makes it so easy to enable TFO on outgoing connections now that I expect many people will blindly run the setsockopt() before connect(). Do not hesitate to ask me to run some tests. While 4 years ago it was not easy, here it's very simple for me. By the way I'm seeing an ~10% performance increase on haproxy by enabling this, it's really cool! Thanks, Willy
