From: Con Kolivas <kernel@kolivas.org>
To: Eric Wong <eric@yhbt.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-ck5 sucks
Date: Sat, 12 Apr 2003 23:16:16 +1000 [thread overview]
Message-ID: <200304122316.16785.kernel@kolivas.org> (raw)
In-Reply-To: <20030412124132.GA3187@BL4ST>
On Sat, 12 Apr 2003 22:41, Eric Wong wrote:
> Con Kolivas <kernel@kolivas.org> wrote:
> > It seems the interactivity patch wasn't worth the effort, confirming my
> > suspicions - which is why I resisted posting it in the first place.
>
> Yikes! I've been indulging in 2.5.67 + anticipatory I/O for bit now,
> back to 2.4...
>
> I finally got around running ck5 with a lot of other odd patches from
> here and there just last night. I wasn't sure if it was ck5 or any
> thing else I put in my kernel that caused it, but the scheduler didn't
> seem to want to work once physical memory was low.
>
> There's a pretty serious bug in the ck5 scheduler where things stop
> running after physical memory is low. Even if the make World jobs are
> cancelled, performance is still sluggish.
<---snip-->
Eric I appreciate the work you've done for ck5, but this is two discrete
problems.
The first is the one you describe with the memory killing the scheduler - a
serious bug.
The second is that the interactivity patch is too slow. It takes up to 5
seconds for xmms skipping (the reference bad program but used everywhere) to
stop. When you first start music it skips all over the place and then settles
down after a while. This is embarassing considering the machines are >1Ghz
cpus and it doesnt happen on p233 with old scheduler. It appears to take less
time the higher the Hz is (makes sense I guess) however higher Hz in 2.4
incurs too much overhead under heavy load. This happens even in 2.5 but is a
bit more subtle.
My concern is that ck6pre without the interactivity addon works better. I've
added the more finegrained scheduler timing and the small bugfix but backed
out the rest. I don't think the interactivity patch in it's current form is
of any use to O(1) 2.4 kernels.
I think Zwane and others have demonstrated that this happens in 2.5 as well so
it needs some work yet to be better than stock.
Con
prev parent reply other threads:[~2003-04-12 13:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 3:23 2.4.20-ck5 sucks Con Kolivas
2003-04-12 12:41 ` Eric Wong
2003-04-12 13:16 ` Con Kolivas [this message]
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=200304122316.16785.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=eric@yhbt.net \
--cc=linux-kernel@vger.kernel.org \
/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.