From: Baruch Even <baruch@ev-en.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Hubert Tonneau <hubert.tonneau@fullpliant.org>,
cliff white <cliffw@osdl.org>,
Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
netdev@oss.sgi.com, Injong Rhee <rhee@eos.ncsu.edu>,
"David S. Miller" <davem@davemloft.net>,
Yee-Ting Li <yee-ting.li@nuim.ie>,
Doug Leith <doug.leith@nuim.ie>
Subject: Re: [RFT] BIC TCP delayed ack compensation
Date: Tue, 22 Feb 2005 23:38:32 +0000 [thread overview]
Message-ID: <421BC278.90400@ev-en.org> (raw)
In-Reply-To: <20050222135046.23f7ec7d@dxpl.pdx.osdl.net>
Stephen Hemminger wrote:
> This patch which was extracted from BIC TCP 1.1 compensates
> for systems (like MaxOSX) that don't ACK every other packet.
> It has no impact for normal transfers, but might help with problems
> with Mac like Hubert found.
We have a version of ABC (Appropriate Byte Counting) implementation of
RFC 3465, which we hope to submit soon for inclusion in the kernel which
should be a more appropriate solution for this. The RFC is a well
defined standard whereas this patch has not received any reviewing by
the networking community.
This solution is just a band-aid for only one congestion control, as
opposed to a generic solution. It is also prone to make BIC more
aggressive according to our testing.
I'll try to post our ABC patch tomorrow, time permitting.
One thing to note is that accounting for delayed acking is not an overly
important feature, from our testing it only speeds up convergence by a
small factor and doesn't change the correctness of the algorithms.
Baruch
next prev parent reply other threads:[~2005-02-22 23:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <050QTJA12@server5.heliogroup.fr>
2005-02-09 18:59 ` 2.6.10 TCP troubles -- suggested patch Stephen Hemminger
2005-02-09 20:25 ` David S. Miller
2005-02-22 21:50 ` [RFT] BIC TCP delayed ack compensation Stephen Hemminger
2005-02-22 23:30 ` John Heffner
2005-02-22 23:38 ` Baruch Even [this message]
2005-02-23 1:04 ` Yee-Ting Li
2005-02-23 15:28 ` Yee-Ting Li
2005-02-22 22:22 Hubert Tonneau
2005-02-23 0:58 ` Stephen Hemminger
2005-02-23 18:32 ` Injong Rhee
2005-02-23 19:36 ` Stephen Hemminger
2005-02-23 18:37 ` Injong Rhee
2005-02-23 19:26 ` David S. Miller
2005-02-23 22:04 ` John Heffner
2005-02-23 22:10 ` David S. Miller
2005-02-23 22:19 ` John Heffner
-- strict thread matches above, loose matches on Subject: below --
2005-02-23 21:54 Hubert Tonneau
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=421BC278.90400@ev-en.org \
--to=baruch@ev-en.org \
--cc=cliffw@osdl.org \
--cc=davem@davemloft.net \
--cc=doug.leith@nuim.ie \
--cc=hubert.tonneau@fullpliant.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=rhee@eos.ncsu.edu \
--cc=shemminger@osdl.org \
--cc=yee-ting.li@nuim.ie \
/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).