From: Robert Love <rml@tech9.net>
To: Andrew Morton <akpm@digeo.com>
Cc: Rick Lindsley <ricklind@us.ibm.com>,
solt@dns.toxicfilms.tv, linux-kernel@vger.kernel.org,
frankeh@us.ibm.com
Subject: Re: must-fix list for 2.6.0
Date: 30 Apr 2003 19:53:25 -0400 [thread overview]
Message-ID: <1051746805.17629.35.camel@localhost> (raw)
In-Reply-To: <20030430162108.09dbd019.akpm@digeo.com>
On Wed, 2003-04-30 at 19:21, Andrew Morton wrote:
> A few kernels ago, OpenOffice would take sixty seconds to just flop down a
> menu if there was a kernel build happening at the same time. That is just
> utterly broken, so if we're going to leave the sched.c code as-is then we
> *require* that all applications be updated to not spin on sched_yield.
Just as a note (I know its not an excuse), Red Hat 9 has Open Office
with the dumb sched_yield() calls removed. It runs quite nice.
> Has anyone looked at what Andrea did in -aa? I assume some suitable
> compromise was achieved there.
Well, his base O(1) scheduler does not have 2.5's sched_yield()... but
he has a patch (I guess that he wrote) on top which changes the
semantics a bit. It looks like he drops the task one priority level
each call, but if it is ever to-be-moved to a queue all by its lonesome,
the task is put on the expired array instead.
Also, he has a check at the start that, if it is in a queue all by
itself (even before it is moved) the call just returns.
Not sure what all these changes add up to...
Robert Love
next prev parent reply other threads:[~2003-04-30 23:41 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 22:57 must-fix list for 2.6.0 Andrew Morton
2003-04-29 23:22 ` John Bradford
2003-04-29 23:37 ` Andrew Morton
2003-04-30 3:19 ` William Lee Irwin III
2003-04-30 4:45 ` Andrew Morton
2003-04-30 4:52 ` William Lee Irwin III
2003-05-01 4:32 ` William Lee Irwin III
2003-04-30 8:30 ` Benjamin Herrenschmidt
2003-04-30 10:16 ` Maciej Soltysiak
2003-04-30 19:11 ` Andrew Morton
2003-04-30 23:11 ` Rick Lindsley
2003-04-30 23:21 ` Andrew Morton
2003-04-30 23:47 ` viro
2003-04-30 23:59 ` Andrew Morton
2003-05-01 6:27 ` Christoph Hellwig
2003-05-01 5:49 ` Shawn
2003-05-01 10:14 ` Christoph Hellwig
2003-05-01 9:47 ` Alan Cox
2003-05-01 15:44 ` Robert Love
2003-05-01 0:09 ` Robert Love
2003-05-01 0:51 ` Gerrit Huizenga
2003-05-01 5:40 ` Dave Hansen
2003-05-01 11:57 ` Bill Huey
2003-04-30 23:53 ` Robert Love [this message]
2003-05-01 8:36 ` Arjan van de Ven
2003-05-01 8:42 ` Andrew Morton
2003-05-01 8:47 ` Arjan van de Ven
2003-04-30 23:41 ` Robert Love
2003-05-01 16:50 ` Hubertus Franke
2003-05-01 3:21 ` Mike Galbraith
2003-05-01 6:26 ` Mike Galbraith
2003-05-01 14:33 ` Christoph Hellwig
2003-05-01 18:42 ` Andrew Morton
2003-05-01 18:47 ` Christoph Hellwig
2003-05-02 1:57 ` Andreas Boman
[not found] <20030429155731.07811707.akpm@digeo.com.suse.lists.linux.kernel>
2003-04-30 1:36 ` Andi Kleen
2003-04-30 18:09 ` Pavel Machek
2003-04-30 18:15 ` Andi Kleen
2003-04-30 19:11 ` Pavel Machek
[not found] <20030429231009$1e6b@gated-at.bofh.it>
2003-04-30 4:55 ` Florian Weimer
2003-04-30 10:18 ` Maciej Soltysiak
2003-05-01 11:24 ` David S. Miller
2003-05-01 11:27 ` Florian Weimer
2003-05-01 12:03 ` David S. Miller
2003-05-01 12:05 ` David S. Miller
2003-05-02 16:28 ` Carl-Daniel Hailfinger
2003-05-02 21:14 ` 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=1051746805.17629.35.camel@localhost \
--to=rml@tech9.net \
--cc=akpm@digeo.com \
--cc=frankeh@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ricklind@us.ibm.com \
--cc=solt@dns.toxicfilms.tv \
/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.