From: Hubert Tonneau <hubert.tonneau@fullpliant.org>
To: Stephen Hemminger <shemminger@osdl.org>,
"Injong Rhee" <rhee@eos.ncsu.edu>
Cc: "'cliff white'" <cliffw@osdl.org>,
"'Alexey Kuznetsov'" <kuznet@ms2.inr.ac.ru>, <netdev@oss.sgi.com>,
"'David S. Miller'" <davem@davemloft.net>
Subject: Re: [RFT] BIC TCP delayed ack compensation
Date: Wed, 23 Feb 2005 21:54:47 GMT [thread overview]
Message-ID: <052RU7B12@server5.heliogroup.fr> (raw)
Stephen Hemminger wrote:
>
> An interesting test would be to repeat the slow case: 2.6.10-ac11 over 100Mbps
>
> With first TCP Reno (old default).
> sysctl -w net.ipv4.tcp_bic=0
No change.
> then TCP Westwood.
> sysctl -w net.ipv4.tcp_bic=0
> sysctl -w net.ipv4.tcp_westwood=1
No change.
Now Linux 2.6.11-rc4 with Injong Rhee abc patch:
No change.
Looks like David S. Miller is right.
Now, what I still don't understand is, if it's PSH/ACK related, why does
the gigabit connected Mac works nicely whereas the 100 Mbps connected one
does not ?
next reply other threads:[~2005-02-23 21:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 21:54 Hubert Tonneau [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2005-02-23 22:04 ` John Heffner
2005-02-23 22:10 ` David S. Miller
2005-02-23 22:19 ` John Heffner
[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=052RU7B12@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.