All of lore.kernel.org
 help / color / mirror / Atom feed
From: davef1624@aol.com
To: davem@davemloft.net, baruch@ev-en.org
Cc: shemminger@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: TCP congestion control for fast, short-distance networks ?
Date: Wed, 04 Apr 2007 16:15:13 -0400	[thread overview]
Message-ID: <8C9450D169515E6-244-1CF0@FWM-D41.sysops.aol.com> (raw)
In-Reply-To: <20070404.125546.87742905.davem@davemloft.net>

thanks for your help - I'll investigate turning on 802.3 level flow 
control


-----Original Message-----
From: davem@davemloft.net
To: baruch@ev-en.org
Cc: davef1624@aol.com; shemminger@linux-foundation.org; 
netdev@vger.kernel.org
Sent: Wed, 4 Apr 2007 12:55 PM
Subject: Re: TCP congestion control for fast, short-distance networks ?

  From: Baruch Even <baruch@ev-en.org>
Date: Wed, 4 Apr 2007 19:11:21 +0300

> * 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.

Congestion control, at the TCP level, is from one perspective
completely senseless on local high-speed networks.  The reason is that
once any kind of congestion at that level is detected, the condition
is gone by the time you could even possibly respond to it.

So with that in mind, reno is as good as anything and yes do use
pause frames.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


________________________________________________________________________
AOL now offers free email to everyone.  Find out more about what's free 
from AOL at AOL.com.

  reply	other threads:[~2007-04-04 20:15 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
2007-04-04 19:55                     ` David Miller
2007-04-04 20:15                       ` davef1624 [this message]
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=8C9450D169515E6-244-1CF0@FWM-D41.sysops.aol.com \
    --to=davef1624@aol.com \
    --cc=baruch@ev-en.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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.