netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pasi Sarolahti <pasi.sarolahti@iki.fi>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "David S. Miller" <davem@redhat.com>,
	netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: [RFC] Vegas and tcp parameters per route
Date: Sat, 13 Mar 2004 08:41:05 +0200	[thread overview]
Message-ID: <1079160064.11606.15.camel@viivi> (raw)
In-Reply-To: <20040312151729.25d9c696@dell_ss3.pdx.osdl.net>

Hi Stephen,

On Sat, 2004-03-13 at 01:17, Stephen Hemminger wrote:
> This is the second more complete version of TCP Vegas that allows setting
> the options based on route.  Reused the RTAX_FEATURE metric which got
> defined but never used, to provide the ability to select vegas, westwood,
> and/or frto per route.
> 
> There is an modified version of iproute2 available at
> 	http://developer.osdl.org/shemminger/tcp/iproute2-exp.tar.bz2
> With this it is possible to setup options per route with ip.
> 	ip route add to 10.0.0.1 features vegas/frto

I would still like to keep the good old sysctl interface (well, at least
for tcp_frto), because I'd belive it is more familiar and easier to use
for many and not dependent of external tools.

Would it be too complicated, if sysctl would give the global default,
from which one can deviate using RTAX_FEATURE?

- Pasi



  reply	other threads:[~2004-03-13  6:41 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 [this message]
2004-03-15 17:20   ` Stephen Hemminger
2004-03-15 21:22     ` David S. Miller
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=1079160064.11606.15.camel@viivi \
    --to=pasi.sarolahti@iki.fi \
    --cc=davem@redhat.com \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --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).