From: Rick Jones <rick.jones2@hp.com>
To: OBATA Noboru <noboru.obata.ar@hitachi.com>
Cc: davem@davemloft.net, 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: Wed, 29 Aug 2007 09:16:43 -0700 [thread overview]
Message-ID: <46D59BEB.1080602@hp.com> (raw)
In-Reply-To: <20070829.212613.65744831.noboru.obata.ar@hitachi.com>
OBATA Noboru wrote:
> What about another option to let TCP have a notification?
>
> Can it be a solution if it is standardized?
It would at best be a partial solution which would only work when the
link failover/whatnot happened on the same system/node as the TCP
endpoint. Then it can be some sort of call-back to TCP or the like.
If this failover is out in the middle of the cloud the only way to get a
notification back to TCP would be by sending it a packet of some sort
and I don't see that happening.
rick jones
next prev parent reply other threads:[~2007-08-29 16:17 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 [this message]
2007-08-30 12:24 ` OBATA Noboru
2007-08-29 18:15 ` David Miller
2007-07-12 20:51 ` Rick Jones
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=46D59BEB.1080602@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.