From: "David S. Miller" <davem@redhat.com>
To: "Injong Rhee" <rhee@eos.ncsu.edu>
Cc: shemminger@osdl.org, netdev@oss.sgi.com, rhee@ncsu.edu,
lxu2@ncsu.edu, mathis@psc.edu
Subject: Re: [RFC] TCP burst control
Date: Tue, 6 Jul 2004 17:29:13 -0700 [thread overview]
Message-ID: <20040706172913.590710fe.davem@redhat.com> (raw)
In-Reply-To: <200407070009.i6709wiA026673@ms-smtp-03-eri0.southeast.rr.com>
On Tue, 6 Jul 2004 20:09:41 -0400
"Injong Rhee" <rhee@eos.ncsu.edu> wrote:
> Currently with rate having, current Linux tcp stack is full of hacks that in
> fact, hurt the performance of linux tcp (sorry to say this).
If rate-halving is broken, have you taken this up with it's creator,
Mr. Mathis? What was his response?
I've added him to the CC: list so this can be properly discussed.
next prev parent reply other threads:[~2004-07-07 0:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-06 22:58 [RFC] TCP burst control Stephen Hemminger
2004-07-06 23:04 ` David S. Miller
2004-07-07 0:09 ` Injong Rhee
2004-07-07 0:29 ` David S. Miller [this message]
2004-07-07 5:46 ` Injong Rhee
2004-07-07 5:49 ` Injong Rhee
2004-07-07 15:31 ` Matt Mathis
2004-07-09 15:36 ` Injong Rhee
2004-07-15 0:11 ` Weiguang Shi
2004-07-07 2:20 ` Nivedita Singhvi
2004-07-28 9:48 ` Xiaoliang (David) Wei
2004-07-28 13:45 ` Lisong Xu
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=20040706172913.590710fe.davem@redhat.com \
--to=davem@redhat.com \
--cc=lxu2@ncsu.edu \
--cc=mathis@psc.edu \
--cc=netdev@oss.sgi.com \
--cc=rhee@eos.ncsu.edu \
--cc=rhee@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).