From: Andi Kleen <ak@muc.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Peter Williams <pwil3058@bigpond.net.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] V-3.0 Single Priority Array O(1) CPU Scheduler Evaluation
Date: 3 Aug 2004 08:51:54 +0200
Date: Tue, 3 Aug 2004 08:51:54 +0200 [thread overview]
Message-ID: <20040803065154.GA85840@muc.de> (raw)
In-Reply-To: <20040802205332.3413cd6d.akpm@osdl.org>
> But let me re-repeat again that CPU scheduler problems tend to take a
> _long_ time to turn up - you make some change and two months later some
> person with a weird workload on expensive hardware hits a nasty corner
> case. So I do think that we'd have to hit a nasty problem with the current
> scheduler to go making deep changes.
How about just simplifying the code? Both Con's and Peter's code
look a lot simpler compared to the stock scheduler and are easier
to understand. If they don't work significantly worse I think that
would be a strong argument to move to one of them.
-Andi
next prev parent reply other threads:[~2004-08-03 6:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2oEEn-197-9@gated-at.bofh.it>
2004-08-02 13:27 ` [PATCH] V-3.0 Single Priority Array O(1) CPU Scheduler Evaluation Andi Kleen
2004-08-03 0:27 ` Peter Williams
2004-08-03 3:53 ` Andrew Morton
2004-08-03 4:38 ` Peter Williams
2004-08-03 6:51 ` Andi Kleen [this message]
2004-08-07 1:44 Peter Williams
-- strict thread matches above, loose matches on Subject: below --
2004-08-02 6:31 Peter Williams
2004-08-02 13:42 ` William Lee Irwin III
2004-08-03 0:33 ` Peter Williams
2004-08-03 2:03 ` William Lee Irwin III
2004-08-03 3:39 ` Peter Williams
2004-08-03 10:49 ` William Lee Irwin III
2004-08-04 0:37 ` Peter Williams
2004-08-04 0:50 ` William Lee Irwin III
2004-08-04 1:36 ` Peter Williams
2004-08-04 1:51 ` William Lee Irwin III
2004-08-04 2:40 ` Peter Williams
2004-08-04 7:05 ` Ingo Molnar
2004-08-04 7:44 ` William Lee Irwin III
2004-08-05 1:06 ` Peter Williams
2004-08-05 2:00 ` William Lee Irwin III
2004-08-05 2:12 ` Peter Williams
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=20040803065154.GA85840@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pwil3058@bigpond.net.au \
/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.