All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: shemminger@osdl.org, ak@suse.de, linux-net@vger.kernel.org,
	netdev@oss.sgi.com
Subject: Re: [RFC] TCP Vegas for 2.6
Date: Mon, 8 Mar 2004 15:31:22 -0800	[thread overview]
Message-ID: <20040308153122.5829617f.davem@redhat.com> (raw)
In-Reply-To: <20040308213646.GH26401@wotan.suse.de>

On Mon, 8 Mar 2004 22:36:46 +0100
Andi Kleen <ak@suse.de> wrote:

> > CONFIG options are of no use vendors who need to ship binary kernels.
> 
> I can well see a vendor trading scalability for experimental non standard TCP 
> algorithms that tend to be disabled anyways.

I explicitly removed the CONFIG_ options guarding the westwood stuff
when I added it to the tree.  I want people to use this stuff, and
I don't want them to have to enable weird config options just to do
so.

      parent reply	other threads:[~2004-03-08 23:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-08 21:04 [RFC] TCP Vegas for 2.6 Stephen Hemminger
2004-03-08 21:21 ` Andi Kleen
2004-03-08 21:30   ` Stephen Hemminger
2004-03-08 21:36     ` Andi Kleen
2004-03-08 21:45       ` Stephen Hemminger
2004-03-08 23:37         ` David S. Miller
2004-03-09 17:52         ` John Heffner
2004-03-09 18:03           ` Andi Kleen
2004-03-09 18:11             ` John Heffner
2004-03-09 18:22               ` Stephen Hemminger
2004-03-09 18:56                 ` Nivedita Singhvi
2004-03-09 19:03                   ` Stephen Hemminger
2004-03-09 19:36                     ` Nivedita Singhvi
2004-03-09 18:58                 ` jamal
2004-03-08 21:51       ` Nivedita Singhvi
2004-03-08 23:31       ` David S. Miller [this message]

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=20040308153122.5829617f.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=ak@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.