From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Baruch Even <baruch@ev-en.org>
Cc: davef1624@aol.com, netdev@vger.kernel.org
Subject: Re: TCP congestion control for fast, short-distance networks ?
Date: Wed, 4 Apr 2007 10:39:44 -0700 [thread overview]
Message-ID: <20070404103944.1b15de16@freekitty> (raw)
In-Reply-To: <20070404161121.GB32019@galon.ev-en.org>
On Wed, 4 Apr 2007 19:11:21 +0300
Baruch Even <baruch@ev-en.org> wrote:
> * davef1624@aol.com <davef1624@aol.com> [070404 19:03]:
> > Thanks - so you are suggesting we enable 802.3 flow-control / pause-frames?
> > (it's currently disabled)
>
> I do, but do test it before you bet on it. I've never tested such a
> scenario but from my experience the lower the rtt the lesser are the
> problems that the high speed algorithms are trying to solve.
>
> Baruch
>
> >
> > -----Original Message-----
> > From: baruch@ev-en.org
> > To: davef1624@aol.com
> > Cc: shemminger@linux-foundation.org; netdev@vger.kernel.org
> > Sent: Wed, 4 Apr 2007 8:39 AM
> > Subject: Re: TCP congestion control for fast, short-distance networks ?
> >
> > * davef1624@aol.com <davef1624@aol.com> [070404 18:29]:
> > >Hello,
> > >
> > >We are currently using both 1 Gb & 10 Gb links, that interconnect
> > several
> > servers that are very *local* to
> > >each other.
> > >Typical RTT times range from 0.2 ms - 0.3 ms.
> > >
> > >We are currently using TCP reno - is there a more suitable congestion
> > control
> > algorithm for our
> > >application,
> > >especially using the 10 Gb links ?
> > >(Most of the High-Speed TCP algorithms seem suitable for large RTT,
> > long-distance networks).
> >
> > I'm not aware of any tests for high speed links with very low RTTs, but
> > I suspect that the new algorithms will not change much, if the
> > connections you have are indeed local than the Ethernet pause mechanism
> > is more effective for the flow control you need.
> >
> > Baruch
Pause helps (if the hardware works). But on very high speed links with low
RTT, your main source of throttling is lack of bus bandwidth on receiver.
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-04-04 17:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070312164311.13b5fcec@freekitty>
[not found] ` <200703142247.l2EMln1o000338@expredir5.cites.uiuc.edu>
2007-04-03 3:15 ` [RFC] TCP Illinois preliminary version Stephen Hemminger
2007-04-03 3:39 ` David Miller
2007-04-03 3:44 ` Stephen Hemminger
2007-04-03 20:20 ` Julian Shao Liu
2007-04-03 20:25 ` Julian Shao Liu
2007-04-03 16:16 ` [PATCH] TCP Illinois congestion control Stephen Hemminger
2007-04-03 21:13 ` Julian Shao Liu
2007-04-04 15:07 ` [PATCH] TCP Illinois congestion control (rev3) Stephen Hemminger
2007-04-04 15:22 ` TCP congestion control for fast, short-distance networks ? davef1624
2007-04-04 15:39 ` Baruch Even
2007-04-04 15:58 ` davef1624
2007-04-04 16:11 ` Baruch Even
2007-04-04 17:39 ` Stephen Hemminger [this message]
2007-04-04 19:55 ` David Miller
2007-04-04 20:15 ` davef1624
2007-04-21 0:08 ` [PATCH] TCP Illinois congestion control (rev3) David Miller
2007-04-21 1:00 ` Stephen Hemminger
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=20070404103944.1b15de16@freekitty \
--to=shemminger@linux-foundation.org \
--cc=baruch@ev-en.org \
--cc=davef1624@aol.com \
--cc=netdev@vger.kernel.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).