From: bert hubert <ahu@ds9a.nl>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "David S. Miller" <davem@redhat.com>, netdev@oss.sgi.com
Subject: Re: [PATCH] mark CSZ scheduler as broken
Date: Wed, 7 Jul 2004 22:32:45 +0200 [thread overview]
Message-ID: <20040707203245.GA9617@outpost.ds9a.nl> (raw)
In-Reply-To: <20040707111936.760586b0@dell_ss3.pdx.osdl.net>
On Wed, Jul 07, 2004 at 11:19:36AM -0700, Stephen Hemminger wrote:
> Since the configuration help for CSZ is broken, and other documentation
> says it just doesn't work. Why not mark it as broken to make it obvious?
For all I care we can zonk it - even Alexey is unclear about its workings or
use. More of a research project then something we should ship.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-07-07 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 18:19 [PATCH] mark CSZ scheduler as broken Stephen Hemminger
2004-07-07 20:32 ` bert hubert [this message]
2004-07-07 22:27 ` David S. Miller
2004-07-07 22:28 ` David S. Miller
2004-07-07 23:56 ` Stephen Hemminger
2004-07-09 23:15 ` 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=20040707203245.GA9617@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=davem@redhat.com \
--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).