From: "David S. Miller" <davem@davemloft.net>
To: "Injong Rhee" <rhee@eos.ncsu.edu>
Cc: hubert.tonneau@fullpliant.org, shemminger@osdl.org,
cliffw@osdl.org, kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Subject: Re: [RFT] BIC TCP delayed ack compensation
Date: Wed, 23 Feb 2005 11:26:11 -0800 [thread overview]
Message-ID: <20050223112611.60561121.davem@davemloft.net> (raw)
In-Reply-To: <200502231835.j1NIZX2T020606@uni07mr.unity.ncsu.edu>
On Wed, 23 Feb 2005 13:37:35 -0500
"Injong Rhee" <rhee@eos.ncsu.edu> wrote:
>
>
> > -----Original Message-----
> > From: Hubert Tonneau [mailto:hubert.tonneau@fullpliant.org]
> > Sent: Tuesday, February 22, 2005 5:23 PM
> > 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
>
> Another way to test whether this is related to the os or bic
> implementation is to test it with our bic patch 1.1. + Linux 2.4. It
> will tell whether the original implementation of BIC has something to
> do with the performance with respect to MacOS.
I don't think BIC has much to do with this problem. MacOS-X does delayed
ACKs until a PSH is seen and this kills performance if we don't PSH often
enough.
next prev parent reply other threads:[~2005-02-23 19:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 22:22 [RFT] BIC TCP delayed ack compensation 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 [this message]
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=20050223112611.60561121.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cliffw@osdl.org \
--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 \
/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).