From: Andi Kleen <ak@suse.de>
To: Alan Cox <alan@redhat.com>
Cc: rml@tech9.net (Robert Love), mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4-ac task->cpu abstraction and optimization
Date: 12 Sep 2002 22:55:20 +0200 [thread overview]
Message-ID: <p73bs73udvr.fsf@oldwotan.suse.de> (raw)
In-Reply-To: Alan Cox's message of "12 Sep 2002 22:28:54 +0200"
Alan Cox <alan@redhat.com> writes:
> > > also took a look at your patch -- looks good, you should submit it to
> > > Marcelo... it cannot hurt for 2.4.
> >
> > I might do that, unless Alan plans on pushing the -ac sched.c stuff to
> > Marcelo, in which case my patch would just confuse things. Alan?
>
> I'd like to see it in 2.4 base. Its really Marcelo's call.
One imho major problem with the new scheduler is that its new
sched_yield breaks programs like OpenOffice, who rely on the old
sched_yield behaviour. With new scheduler and 2.5 yield OpenOffice
can be completely starved just by a kernel compile because sched_yield
kills all its time slices.
I don't think a stable release should break programs in such a way.
-Andi
next parent reply other threads:[~2002-09-12 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15744.57073.2852.707839@kim.it.uu.se.suse.lists.linux.kernel>
[not found] ` <200209122022.g8CKMJS15137@devserv.devel.redhat.com.suse.lists.linux.kernel>
2002-09-12 20:55 ` Andi Kleen [this message]
2002-09-12 21:58 ` [PATCH] 2.4-ac task->cpu abstraction and optimization Alan Cox
2002-09-11 22:21 Robert Love
2002-09-12 6:52 ` Mikael Pettersson
2002-09-12 18:23 ` Robert Love
2002-09-12 18:37 ` Mikael Pettersson
2002-09-12 20:22 ` Alan Cox
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=p73bs73udvr.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
/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.