netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: "David S. Miller" <davem@davemloft.net>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	davem@redhat.com, netdev@oss.sgi.com
Subject: Re: [PATCH] (1/3) tcp - choose congestion algorithm at initialization
Date: Tue, 28 Sep 2004 09:08:54 -0700	[thread overview]
Message-ID: <1096387734.21799.1.camel@localhost.localdomain> (raw)
In-Reply-To: <20040927225858.3a1665f1.davem@davemloft.net>

On Mon, 2004-09-27 at 22:58 -0700, David S. Miller wrote:
> On Tue, 28 Sep 2004 08:07:36 +1000
> Herbert Xu <herbert@gondor.apana.org.au> wrote:
> 
> > Stephen Hemminger <shemminger@osdl.org> wrote:
> > > The choice of congestion algorithm needs to be made when connection
> > > is setup to avoid problems when the sysctl values change later and the
> > > necessary data hasn't been collected.
> > 
> > Could this be chosen by a setsockopt as well?
> 
> If we export such things with a user visible
> interface, that makes it harder to rip out the
> congestion control algorithm later.  Such an
> action is very likely so...

The current set of algorithm's is because we haven't found the right
one. If it turns out there are multiple algortihm's that make sense to
support long term, then the choice should be done in as route hints
not as part of the user API.

      reply	other threads:[~2004-09-28 16:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27 18:18 [PATCH] (1/3) tcp - choose congestion algorithm at initialization Stephen Hemminger
2004-09-27 19:16 ` David S. Miller
2004-10-01 22:55   ` Stephen Hemminger
2004-10-03 21:52     ` David S. Miller
2004-10-04 12:42   ` Angelo Dell'Aera
2004-09-27 22:07 ` Herbert Xu
2004-09-28  5:58   ` David S. Miller
2004-09-28 16:08     ` Stephen Hemminger [this message]

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=1096387734.21799.1.camel@localhost.localdomain \
    --to=shemminger@osdl.org \
    --cc=davem@davemloft.net \
    --cc=davem@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@oss.sgi.com \
    /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).