From: Andrew Morton <akpm@digeo.com>
To: Rick Lindsley <ricklind@us.ibm.com>
Cc: solt@dns.toxicfilms.tv, linux-kernel@vger.kernel.org, frankeh@us.ibm.com
Subject: Re: must-fix list for 2.6.0
Date: Wed, 30 Apr 2003 16:21:08 -0700 [thread overview]
Message-ID: <20030430162108.09dbd019.akpm@digeo.com> (raw)
In-Reply-To: <200304302311.h3UNB2H27134@owlet.beaverton.ibm.com>
Rick Lindsley <ricklind@us.ibm.com> wrote:
>
> Why is this bad?
> (a) if it does busy looping through sched_yield it will eat cycles which
> might not have happened
Things like OpenOffice _do_ busy loop on sched_yield(). It appears with
that patch, OO will sit there chewing ~1% of CPU. Not great, but not bad
either..
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.
There's just no question about that. It may end up not being acceptable.
Has anyone looked at what Andrea did in -aa? I assume some suitable
compromise was achieved there.
next prev parent reply other threads:[~2003-04-30 23:11 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 [this message]
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
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=20030430162108.09dbd019.akpm@digeo.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox