Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 5 Feb 2003 16:57:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 5 Feb 2003 16:57:35 -0500 Received: from quechua.inka.de ([193.197.184.2]:29114 "EHLO mail.inka.de") by vger.kernel.org with ESMTP id ; Wed, 5 Feb 2003 16:57:34 -0500 To: linux-kernel@vger.kernel.org Subject: Re: disabling nagle References: Organization: private Linux site, southern Germany Date: Wed, 05 Feb 2003 22:58:25 +0100 From: Olaf Titz Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1246 Lines: 23 > would be to create a patch to disable TCP's timeout and retransmit > mechanisms on a given interface? This would allow those of us who have no > alternative other than PPP over ssh for VPN to greatly improve performance. > Over a well behaved connection this works acceptably, but given any delays > or packet loss it is essentially unusable. I know the real answer is using > something other than TCP as the transport layer for the tunnel (IPSEC, IP > over IP, UDP, etc.) but that isn't always possible. So I'd like a way to > treat the ppp interface the VPN tunnel creates as a completely reliable > transport for which normal TCP/IP retransmits and timeouts don't apply. As I see it, this wouldn't help when the TCP retransmits are originated by a machine other than the VPN routers, because they don't know about the new reliability characteristics of their transport medium. So in any network with more than two machines its usefulness is rather limited. (Or am I missing something?) Olaf - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/