From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Arnd Hannemann <hannemann@nets.rwth-aachen.de>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
"H.K. Jerry Chu" <hkchu@google.com>, <ilpo.jarvinen@helsinki.fi>,
<davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: [PATCH] TCP_FAILFAST: a new socket option to timeout/abort a connection quicker
Date: Tue, 24 Aug 2010 11:10:44 +0200 [thread overview]
Message-ID: <423116d1d215b0fb3d1c966fb8167508@localhost> (raw)
In-Reply-To: <4C737D15.5060400@nets.rwth-aachen.de>
On Tue, 24 Aug 2010 10:04:37 +0200, Arnd Hannemann wrote:
> Why not call it TCP_USERTIMEOUT?
> Later you can also send it via the TCP user timeout option... (RFC5482)
> Hmm... is the ms granularity really needed? Does it make sense to abort
> a connection below a second?
I am working on a patch for UTO, the lion share is already implemented. As
I can see this patch introduce a upper limit (max) where UTO on the other
hand provides a lower limit (min). Therefore I am not sure if we should
call this option TCP_USERTIMEOUT.
Cheers, Hagen
next prev parent reply other threads:[~2010-08-24 9:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 6:20 [PATCH] TCP_FAILFAST: a new socket option to timeout/abort a connection quicker H.K. Jerry Chu
2010-08-24 6:44 ` Eric Dumazet
2010-08-24 8:04 ` Arnd Hannemann
2010-08-24 9:10 ` Hagen Paul Pfeifer [this message]
2010-08-24 14:58 ` Arnd Hannemann
2010-08-24 16:28 ` Hagen Paul Pfeifer
2010-08-24 22:13 ` Jerry Chu
2010-08-25 8:21 ` Hagen Paul Pfeifer
2010-08-25 20:20 ` Jerry Chu
2010-08-25 22:59 ` Hagen Paul Pfeifer
2010-08-26 1:49 ` Jerry Chu
2010-08-26 6:01 ` Lars Eggert
2010-08-26 7:12 ` Arnd Hannemann
2010-08-26 7:42 ` Hagen Paul Pfeifer
2010-08-26 7:27 ` Hagen Paul Pfeifer
2010-08-24 21:56 ` Jerry Chu
2010-08-24 20:47 ` Jerry Chu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=423116d1d215b0fb3d1c966fb8167508@localhost \
--to=hagen@jauu.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=hannemann@nets.rwth-aachen.de \
--cc=hkchu@google.com \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).