From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: pasi.sarolahti@iki.fi, netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: [RFC] Vegas and tcp parameters per route
Date: Mon, 15 Mar 2004 13:22:14 -0800 [thread overview]
Message-ID: <20040315132214.4d9b5347.davem@redhat.com> (raw)
In-Reply-To: <20040315092018.1e843d83@dell_ss3.pdx.osdl.net>
On Mon, 15 Mar 2004 09:20:18 -0800
Stephen Hemminger <shemminger@osdl.org> 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. :-)
next prev parent reply other threads:[~2004-03-15 21:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 23:17 [RFC] Vegas and tcp parameters per route Stephen Hemminger
2004-03-13 6:41 ` Pasi Sarolahti
2004-03-15 17:20 ` Stephen Hemminger
2004-03-15 21:22 ` David S. Miller [this message]
2004-03-15 21:29 ` Andi Kleen
2004-03-15 21:30 ` Stephen Hemminger
2004-03-15 21:37 ` David S. Miller
2004-03-15 17:38 ` YOSHIFUJI Hideaki / 吉藤英明
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=20040315132214.4d9b5347.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pasi.sarolahti@iki.fi \
--cc=shemminger@osdl.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).