netdev
[Top] [All Lists]

Re: [RFC] Vegas and tcp parameters per route

To: Stephen Hemminger <shemminger@xxxxxxxx>
Subject: Re: [RFC] Vegas and tcp parameters per route
From: "David S. Miller" <davem@xxxxxxxxxx>
Date: Mon, 15 Mar 2004 13:22:14 -0800
Cc: pasi.sarolahti@xxxxxx, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx
In-reply-to: <20040315092018.1e843d83@xxxxxxxxxxxxxxxxxxxxx>
References: <20040312151729.25d9c696@xxxxxxxxxxxxxxxxxxxxx> <1079160064.11606.15.camel@viivi> <20040315092018.1e843d83@xxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Mon, 15 Mar 2004 09:20:18 -0800
Stephen Hemminger <shemminger@xxxxxxxx> wrote:

> > Would it be too complicated, if sysctl would give the global default,
> > from which one can deviate using RTAX_FEATURE?
> 
> Maybe for frto it needs to stay, but sysctl's are more painful and complex
> than keeping the stuff in the routing info.  Also, the external tools are
> part of every distro, except for a few embedded systems, the networking code
> depends on user tools already.

How do you propose to support some kind of "global enable" for features.

I think sysctl's support this quite well.  The test for the feature
becomes "sysctl || route_attribute".

Also, as Yoshfuji stated, you absolutely cannot change the existing
sysctl numbers as tools that use the sysctl() system call use those
numbers explicitly thus they are compiled into applications.

I really am not going to consider something that removes existing
sysctl tunables. :-)

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