From: "David S. Miller" <davem@davemloft.net>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org, stable@kernel.org,
shemminger@osdl.org, netdev@oss.sgi.com
Subject: Re: [07/08] [TCP] Fix BIC congestion avoidance algorithm error
Date: Tue, 5 Apr 2005 11:26:08 -0700 [thread overview]
Message-ID: <20050405112608.0b3c07f0.davem@davemloft.net> (raw)
In-Reply-To: <20050405182202.GA11979@thunk.org>
On Tue, 5 Apr 2005 14:22:02 -0400
Theodore Ts'o <tytso@mit.edu> wrote:
> If the congestion control alogirthm is "Reno-like", what is
> user-visible impact to users? There are OS's out there with TCP/IP
> stacks that are still using Reno, aren't there?
An incorrect implementation of any congestion control algorithm
has ramifications not considered when the congestion control
author verified the design of his algorithm.
This has a large impact on every user on the internet, not just
Linux machines.
Perhaps on a microscopic scale "this" part of the BIC algorithm
was just behaving Reno-like due to the bug, but what implications
does that error have as applied to the other heuristics in BIC?
This is what I'm talking about. BIC operates in several modes,
one of which is a pseudo binary search mode, and another is a
less aggressive slower increase mode.
Therefore I think fixes to congestion control algorithms which
are enabled by default always should take a high priority in
the stable kernels.
next prev parent reply other threads:[~2005-04-05 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050405164539.GA17299@kroah.com>
2005-04-05 16:47 ` [05/08] [IPSEC]: Do not hold state lock while checking size Greg KH
2005-04-05 16:47 ` [07/08] [TCP] Fix BIC congestion avoidance algorithm error Greg KH
2005-04-05 18:22 ` Theodore Ts'o
2005-04-05 18:26 ` David S. Miller [this message]
2005-04-05 18:32 ` Stephen Hemminger
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=20050405112608.0b3c07f0.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
--cc=stable@kernel.org \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).