From: Pierfrancesco Caci <ik5pvx@penny.ik5pvx.ampr.org>
To: linux-kernel@vger.kernel.org
Subject: Re: MTU and 2.4.x kernel
Date: 18 Feb 2001 12:26:09 +0100 [thread overview]
Message-ID: <87u25sb5bi.fsf@penny.ik5pvx.ampr.org> (raw)
In-Reply-To: <200102152041.XAA21220@ms2.inr.ac.ru>
In-Reply-To: <200102152041.XAA21220@ms2.inr.ac.ru>
:-> "kuznet" == kuznet <kuznet@ms2.inr.ac.ru> writes:
>> Over a radio link where
>> error rate causes exponential increases in probability of packet loss as
> Another myth. All they do error correction and have so high latency,
> that _increasing_ mtu only helps. And helps a lot.
Please don't break existing implementations. Some old hardware used in
the amateur radio world doesn't even accept an mtu longer than 256(*),
and the resulting packets will be silently chopped at the end.
If you want to drop mtu lower than 512, please at least add a
CONFIG_I_NEED_A_GODDAMN_SMALL_MTU as an option.
Pf
(*) Kantronics TNCs are an example.
--
-------------------------------------------------------------------------------
Pierfrancesco Caci | ik5pvx | mailto:p.caci@tin.it - http://gusp.dyndns.org
Firenze - Italia | Office for the Complication of Otherwise Simple Affairs
Linux penny 2.4.1 #1 Sat Feb 3 20:43:54 CET 2001 i686 unknown
next prev parent reply other threads:[~2001-02-18 11:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 20:39 roger
2001-02-14 20:51 ` Alan Cox
2001-02-15 18:21 ` kuznet
2001-02-15 18:47 ` Alan Cox
2001-02-15 19:33 ` kuznet
2001-02-15 20:27 ` Alan Cox
2001-02-15 20:41 ` kuznet
2001-02-15 21:01 ` Alan Cox
2001-02-18 19:53 ` kuznet
2001-02-19 1:44 ` Alan Cox
2001-02-19 18:26 ` kuznet
2001-02-19 22:20 ` Rick Jones
2001-02-16 12:54 ` Rik van Riel
2001-02-18 11:26 ` Pierfrancesco Caci [this message]
2001-02-16 12:51 ` Rik van Riel
2001-02-18 19:55 ` kuznet
2001-02-18 9:39 ` David S. Miller
2001-02-18 20:17 ` kuznet
2001-02-18 20:32 ` kuznet
2001-02-15 20:40 ` Rick Jones
2001-02-15 20:54 ` Jordan Mendelson
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=87u25sb5bi.fsf@penny.ik5pvx.ampr.org \
--to=ik5pvx@penny.ik5pvx.ampr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p.caci@tin.it \
/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
all inboxes | Powered by JetHome®