From: Olaf Titz <olaf@bigred.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: disabling nagle
Date: Wed, 05 Feb 2003 22:58:25 +0100 [thread overview]
Message-ID: <E18gXYn-0002si-00@bigred.inka.de> (raw)
In-Reply-To: F137jnt61tqeaVRMPjc00012673@hotmail.com
> 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
next prev parent reply other threads:[~2003-02-05 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 0:01 disabling nagle Dave Slicer
2003-02-05 6:47 ` Denis Vlasenko
2003-02-05 17:18 ` Mika Liljeberg
2003-02-06 6:35 ` Denis Vlasenko
2003-02-05 21:58 ` Olaf Titz [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-04 19:39 Fiona Sou-Yee Wong
2003-02-04 19:52 ` Mark Mielke
2003-02-04 20:10 ` Richard B. Johnson
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=E18gXYn-0002si-00@bigred.inka.de \
--to=olaf@bigred.inka.de \
--cc=linux-kernel@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