[Top] [All Lists]

Re: [PATCH] (1/3) tcp - choose congestion algorithm at initialization

To: "David S. Miller" <davem@xxxxxxxxxxxxx>
Subject: Re: [PATCH] (1/3) tcp - choose congestion algorithm at initialization
From: Stephen Hemminger <shemminger@xxxxxxxx>
Date: Tue, 28 Sep 2004 09:08:54 -0700
Cc: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>, davem@xxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20040927225858.3a1665f1.davem@xxxxxxxxxxxxx>
Organization: Open Source Development Lab
References: <20040927111834.48c7baab@xxxxxxxxxxxxxxxxx> <E1CC3ei-00020G-00@xxxxxxxxxxxxxxxxxxxxxxxx> <20040927225858.3a1665f1.davem@xxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxx> wrote:
> > Stephen Hemminger <shemminger@xxxxxxxx> 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.

<Prev in Thread] Current Thread [Next in Thread>