Lars Marowsky-Bree wrote: > If connect() suddenly did two connection attempts instead of one, just how > many timeouts might that break? Timeouts are already broken by applications that repeatedly call connect(). You'd get better timeout behaviour by letting the kernel enforce backoff. > > Why? The connection is dead, but there is nothing to prevent attempting > > another connection. > > Right. And thats why connect() returns an error and retries are handled in > userspace. And this is fine. Can we be permitted to handle a retry in userspace without fancy options (ECN, SACK, large windows etc.)? -- Jamie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: hotmail not dealing with ECN James Sutherland
- Re: hotmail not dealing with ECN David S. Miller
- Re: hotmail not dealing with ECN Jamie Lokier
- Re: hotmail not dealing with ECN James Sutherland
- Re: hotmail not dealing with ECN Lars Marowsky-Bree
- Re: hotmail not dealing with ECN James Sutherland
- Re: hotmail not dealing with ECN Chris Ricker
- Re: hotmail not dealing with ECN Henning P. Schmiedehausen
- Re: hotmail not dealing with ECN Matti Aarnio
- Re: hotmail not dealing with ECN Jeremy M. Dolan
- Re: hotmail not dealing with ECN Jamie Lokier
- Re: hotmail not dealing with ECN Drago Goricanec
- Re: hotmail not dealing with ECN Jamie Lokier
- Re: hotmail not dealing with ECN Olaf Titz
- Re: hotmail not dealing with ECN Jamie Lokier
- Re: hotmail not dealing with ECN David S. Miller
- Re: hotmail not dealing with ECN Lars Marowsky-Bree
- Re: hotmail not dealing with ECN David S. Miller
- Re: hotmail not dealing with ECN Jamie Lokier
- Re: hotmail not dealing with ECN Thunder from the hill
- Re: hotmail not dealing with ECN Thunder from the hill