From: "David S. Miller" <davem@redhat.com>
To: dlstevens@us.ibm.com
Cc: matti.aarnio@zmailer.org, niv@us.ibm.com,
alan@lxorguk.ukuu.org.uk, stefano.andreani.ap@h3g.it,
linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: R: Kernel bug handling TCP_RTO_MAX?
Date: Thu, 12 Dec 2002 22:59:12 -0800 (PST) [thread overview]
Message-ID: <20021212.225912.115906105.davem@redhat.com> (raw)
In-Reply-To: <OF38D59D15.E0619D28-ON88256C8E.0023807F@us.ibm.com>
From: David Stevens <dlstevens@us.ibm.com>
Date: Thu, 12 Dec 2002 23:55:35 -0700
I believe the very large BSD number was based on the large
granularity of the timer (500ms for slowtimeout), designed for use on a VAX
780. The PC on my desk is 3500 times faster than a VAX 780, and you can
send a lot of data on Gigabit Ethernet instead of sitting on your hands for
an enormous min timeout on modern hardware. Switched gigabit isn't exactly
the same kind of environment as shared 10 Mbps (or 2 Mbps) when that stuff
went in, but the min timeouts are the same.
This is well understood, the problem is that BSD's coarse timers are
going to cause all sorts of problems when a Linux stack with a reduced
MIN RTO talks to it.
Consider also, delayed ACKs and possible false retransmits this could
induce with a smaller MIN RTO.
next prev parent reply other threads:[~2002-12-13 6:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 6:55 R: Kernel bug handling TCP_RTO_MAX? David Stevens
2002-12-13 6:59 ` David S. Miller [this message]
2002-12-13 11:46 ` Bogdan Costescu
2002-12-13 11:48 ` Andrew McGregor
2002-12-13 12:33 ` Bogdan Costescu
2002-12-13 13:07 ` Andrew McGregor
2002-12-13 18:07 ` Nivedita Singhvi
2002-12-13 22:25 ` Andrew McGregor
2002-12-13 22:58 ` Matti Aarnio
-- strict thread matches above, loose matches on Subject: below --
2002-12-12 20:37 Nivedita Singhvi
2002-12-12 20:18 Andreani Stefano
2002-12-12 20:32 ` David S. Miller
2002-12-12 21:16 ` Alan Cox
2002-12-13 2:26 ` Nivedita Singhvi
2002-12-13 3:39 ` Matti Aarnio
2002-12-13 4:45 ` Nivedita Singhvi
2002-12-13 6:26 ` Nivedita Singhvi
2002-12-13 11:40 ` Andrew McGregor
2002-12-13 5:23 ` David S. Miller
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=20021212.225912.115906105.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dlstevens@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=matti.aarnio@zmailer.org \
--cc=niv@us.ibm.com \
--cc=stefano.andreani.ap@h3g.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