netdev - Re: [PATCH 2.6.22] TCP: Make TCP_RTO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46D59BEB.1080602@hp.com>
Date:	Wed, 29 Aug 2007 09:16:43 -0700
From:	Rick Jones <rick.jones2@...com>
To:	OBATA Noboru <noboru.obata.ar@...achi.com>
Cc:	davem@...emloft.net, shemminger@...ux-foundation.org,
	yoshfuji@...ux-ipv6.org, netdev@...r.kernel.org
Subject: Re: [PATCH 2.6.22] TCP: Make TCP_RTO_MAX a variable (take 2)

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
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html