Messages in this thread | | | From | Denis Vlasenko <> | Subject | Re: disabling nagle | Date | Thu, 6 Feb 2003 08:35:29 +0200 |
| |
> > > 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. It'd just > > > bullheadedly go along transmitting data and assuming it was > > > received -- the underlying TCP transport can take care of making > > > the link reliable. > > > > I want this too ;) For one, it would be a perfect example of using > > good existing tools to achieve the goal instead of inventing > > something big and new. Also it does not reduce MTU unlike > > packet-encapsulation tunnels. > > > > Now it's an imperfect example due to noted TCP over TCP performance > > problem ('internal meltdown'). > > I doubt a hack like disabling RTO would make it into the kernel. > However, try enabling F-RTO at both ends (echo 1 > > /proc/sys/net/ipv4/tcp_frto). This should improve things quite a bit. > > You need at least linux 2.4.21-pre3, or linux 2.5.x.
Wow, thanks! I'll look into it! (Found the draft. Google is cool ;)
What is really needed is raising RTO to large fixed value so that TCP connection times out before RTs are triggered. And it have to be done only on pppd-over-ssh iface. Am I right that currently kernel TCP options are global, not per-if? -- vda - 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/
| |