From: Andrew Rodland <arodland@noln.com>
To: linux-kernel@vger.kernel.org
Cc: Adrian Bunk <bunk@fs.tum.de>
Subject: Re: [OKS] O(1) scheduler in 2.4
Date: Fri, 5 Jul 2002 03:02:32 -0400 [thread overview]
Message-ID: <20020705030232.2b47515f.arodland@noln.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0207050840140.14934-100000@mimas.fachschaften.tu-muenchen.de>
On Fri, 5 Jul 2002 08:56:59 +0200 (CEST)
Adrian Bunk <bunk@fs.tum.de> wrote:
> On Fri, 5 Jul 2002, Andrew Rodland wrote:
>
> >...
> > Very nearly off topic, but I've had a few people on IRC tell me that
> > they love O(1) specifically because it has a 'nice that actually
> > does something'. As a matter of fact, I've had to change my X
> > startup scripts, to make it a bit less selfish; the defaults are
> > just plain silly, now.
> >...
>
> This is exactly a reason why O(1) shouldn't go into 2.4:
>
> E.g. my X is as suggested by my the installation routine of my
> distribution (Debian unstable/testing) niced to -10. It would be a bad
> surprise for _many_ people if they upgrade their 2.4 kernel because of
> other security and/or stability fixes and such a setting is then
> wrong.
>
Same setup, actually -- I changed it to -3 and it seems nicer.
As for it going into 2.4, well, I'm not incredibly strongly for it, but
I do get a feeling that most of the distros (especially the ones famous
for patching their kernels beyond recognizabliity) will start jumping on
this particular wagon soon. Does the kernel want to be like debian
("Well, yeah, the releases are horribly out of date, but normal human
beings don't actually _use_ the releases") ?
P.S. Do not suppose from this message that I do not love debian
immensely. :)
next prev parent reply other threads:[~2002-07-05 7:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 17:52 [OKS] O(1) scheduler in 2.4 Bill Davidsen
2002-07-01 18:12 ` Tom Rini
2002-07-01 23:44 ` J.A. Magallon
2002-07-02 2:48 ` Tom Rini
2002-07-03 1:11 ` Rob Landley
2002-07-03 7:30 ` Adrian Bunk
2002-07-03 8:35 ` Ingo Molnar
2002-07-04 3:36 ` Bill Davidsen
2002-07-04 6:56 ` Ingo Molnar
2002-07-04 7:36 ` J Sloan
2002-07-05 6:18 ` Andrew Rodland
2002-07-05 6:56 ` Adrian Bunk
2002-07-05 7:02 ` Andrew Rodland [this message]
2002-07-05 9:12 ` William Lee Irwin III
2002-07-04 18:08 ` Rob Landley
2002-07-05 11:17 ` Bill Davidsen
2002-07-05 15:09 ` Rob Landley
2002-07-06 4:31 ` Bill Davidsen
2002-07-06 23:10 ` Rob Landley
2002-07-07 10:55 ` Bill Davidsen
2002-07-02 16:05 ` venom
2002-07-02 16:53 ` Tomas Szepe
2002-07-02 14:46 ` Bill Davidsen
2002-07-02 15:12 ` Tom Rini
2002-07-04 4:02 ` Bill Davidsen
2002-07-04 4:17 ` Tom Rini
2002-07-01 18:49 ` Ingo Molnar
2002-07-02 15:07 ` Bill Davidsen
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=20020705030232.2b47515f.arodland@noln.com \
--to=arodland@noln.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.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