From: Andrew Morton <akpm@digeo.com>
To: Maciej Soltysiak <solt@dns.toxicfilms.tv>
Cc: linux-kernel@vger.kernel.org
Subject: Re: must-fix list for 2.6.0
Date: Wed, 30 Apr 2003 12:11:05 -0700 [thread overview]
Message-ID: <20030430121105.454daee1.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.51.0304301212130.1728@dns.toxicfilms.tv>
Maciej Soltysiak <solt@dns.toxicfilms.tv> wrote:
>
> > kernel/
> > -------
> >
> > - O(1) scheduler starvation, poor behaviour seems unresolved.
> >
> > Jens: "I've been running 2.5.67-mm3 on my workstation for two days, and
> > it still doesn't feel as good as 2.4. It's not a disaster like some
> > revisisons ago, but it still has occasional CPU "stalls" where it feels
> > like a process waits for half a second of so for CPU time. That's is very
> > noticable."
> Well, i had similar problems with 2.5 stalling, but now that i disabled
> preemtible kernel, it is better now. Are there no complaints about preemt?
I have not heard of any, apart from yours.
> Also there is one issue, i am not sure if this may be a kernel issue,
> but with setiathome running in a X desktop environment all apps work fine,
> but when i run openoffice, openoffice responds with 5 second delay.
That'll be the changed sched_yield() semantics.
The below patch should fix that up, but we need to decide whether the (rather
unclear) advantages of the sched_yield() change outweigh the breakage which
it caused linuxthreads applications.
diff -puN kernel/sched.c~sched_yield-hack kernel/sched.c
--- 25/kernel/sched.c~sched_yield-hack 2003-04-30 12:08:51.000000000 -0700
+++ 25-akpm/kernel/sched.c 2003-04-30 12:09:11.000000000 -0700
@@ -1992,7 +1992,7 @@ asmlinkage long sys_sched_yield(void)
*/
if (likely(!rt_task(current))) {
dequeue_task(current, array);
- enqueue_task(current, rq->expired);
+ enqueue_task(current, array);
} else {
list_del(¤t->run_list);
list_add_tail(¤t->run_list, array->queue + current->prio);
_
next prev parent reply other threads:[~2003-04-30 18:58 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 22:57 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 [this message]
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
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=20030430121105.454daee1.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®