netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: Stephen Hemminger <shemminger@osdl.org>,
	linux-net <linux-net@vger.kernel.org>,
	netdev@oss.sgi.com
Subject: Re: [RFC] TCP Vegas for 2.6
Date: Mon, 08 Mar 2004 13:51:17 -0800	[thread overview]
Message-ID: <404CEAD5.9080304@us.ibm.com> (raw)
In-Reply-To: <20040308213646.GH26401@wotan.suse.de>

Andi Kleen wrote:

>>CONFIG options are of no use vendors who need to ship binary kernels.

But they are real handy to developers and benchmarking
folks who are trying to evaluate their impact and need
to compare with/without :)

> I can well see a vendor trading scalability for experimental non standard TCP 
> algorithms that tend to be disabled anyways.
> 
> Or allocating separately if you prefer that. In theory it may be even
> possible to change the slab cache size at runtime, but that could get tricky.

It would be nice to minimize this if possible, but
keep in mind that dynamic allocation of memory (and freeing
it) is among the costliest performance hits we take..

thanks,
Nivedita

  parent reply	other threads:[~2004-03-08 21:51 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 [this message]
2004-03-08 23:31       ` David S. Miller

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=404CEAD5.9080304@us.ibm.com \
    --to=niv@us.ibm.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 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).