From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: noboru.obata.ar@hitachi.com, shemminger@linux-foundation.org,
yoshfuji@linux-ipv6.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2)
Date: Thu, 12 Jul 2007 13:51:44 -0700 [thread overview]
Message-ID: <46969460.3020604@hp.com> (raw)
In-Reply-To: <20070712.023710.36923635.davem@davemloft.net>
>
> TCP's timeouts are perfectly fine, and the only thing you
> might be showing above is that the application timeouts
> are too short or that TCP needs notifications.
The application timeouts are probably being driven by external desires
for a given recovery time.
TCP notifications don't solve anything unless the links in question are
local to the machine on which the TCP endpoint resides.
So, it seems that what this is really saying is that in the context of
Linux at least, TCP is not a suitable protocol to be used in situations
where a fast detection/recovery is desired.
Does that pretty much sum it up?
rick jones
next prev parent reply other threads:[~2007-07-12 20:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 7:15 [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2) OBATA Noboru
2007-07-12 9:37 ` David Miller
2007-07-12 13:59 ` OBATA Noboru
2007-07-12 20:24 ` David Miller
2007-07-12 21:12 ` Stephen Hemminger
2007-07-12 21:27 ` Rick Jones
2007-07-12 22:02 ` Stephen Hemminger
2007-07-12 22:27 ` Rick Jones
2007-07-24 13:30 ` OBATA Noboru
2007-07-13 4:29 ` Ilpo Järvinen
2007-07-13 16:55 ` Rick Jones
2007-07-14 6:19 ` David Miller
2007-07-23 18:40 ` Rick Jones
[not found] ` <20070828.220447.01366772.noboru.obata.ar@hitachi.com>
[not found] ` <20070828.133057.107937654.davem@davemloft.net>
2007-08-29 12:26 ` OBATA Noboru
2007-08-29 16:16 ` Rick Jones
2007-08-30 12:24 ` OBATA Noboru
2007-08-29 18:15 ` David Miller
2007-07-12 20:51 ` Rick Jones [this message]
2007-07-24 13:35 ` OBATA Noboru
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=46969460.3020604@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=noboru.obata.ar@hitachi.com \
--cc=shemminger@linux-foundation.org \
--cc=yoshfuji@linux-ipv6.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).