From: Hubert Tonneau <hubert.tonneau@fullpliant.org>
To: Stephen Hemminger <shemminger@osdl.org>, cliff white <cliffw@osdl.org>
Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
netdev@oss.sgi.com, Injong Rhee <rhee@eos.ncsu.edu>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [RFT] BIC TCP delayed ack compensation
Date: Tue, 22 Feb 2005 22:22:42 GMT [thread overview]
Message-ID: <052Q0TU11@server5.heliogroup.fr> (raw)
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.
No, it's even worse.
2.6.9 to 100 Mbps connected MacOSX: 15 seconds (for roughly 100 MB or data)
2.6.9 to gigabit connected MacOSX: 5 seconds
2.6.10-ac11 to 100 Mbps connected MacOSX: 325 seconds
2.6.10-ac11 to gigabit connected MacOSX: 5 seconds
2.6.10-ac11+BIC to 100 Mbps connected MacOSX: 620 seconds
2.6.10-ac11+BIC to gigabit connected MacOSX: 5 seconds
next reply other threads:[~2005-02-22 22:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 22:22 Hubert Tonneau [this message]
2005-02-23 0:58 ` [RFT] BIC TCP delayed ack compensation 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
[not found] <050QTJA12@server5.heliogroup.fr>
2005-02-09 18:59 ` 2.6.10 TCP troubles -- suggested patch Stephen Hemminger
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
2005-02-23 1:04 ` Yee-Ting Li
2005-02-23 15:28 ` Yee-Ting Li
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=052Q0TU11@server5.heliogroup.fr \
--to=hubert.tonneau@fullpliant.org \
--cc=cliffw@osdl.org \
--cc=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=rhee@eos.ncsu.edu \
--cc=shemminger@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.