From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: Stephen Hemminger <shemminger@osdl.org>,
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 22:29:35 +0100 [thread overview]
Message-ID: <20040315212935.GB20830@wotan.suse.de> (raw)
In-Reply-To: <20040315132214.4d9b5347.davem@redhat.com>
> 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.
Actually it is fine these days. Numerical sysctl is deprecated
and should be removed soon.
-Andi
next prev parent reply other threads:[~2004-03-15 21:29 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
2004-03-15 21:29 ` Andi Kleen [this message]
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=20040315212935.GB20830@wotan.suse.de \
--to=ak@suse.de \
--cc=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).