From: Con Kolivas <kernel@kolivas.org>
To: Tom Sightler <ttsig@tuxyturvy.com>
Cc: "ismail (cartman) donmez" <kde@myrealbox.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.74-mm1 and Con Kolivas' CPU scheduler work
Date: Fri, 4 Jul 2003 14:25:29 +1000 [thread overview]
Message-ID: <200307041425.29828.kernel@kolivas.org> (raw)
In-Reply-To: <1057291914.5681.11.camel@iso-8590-lx.zeusinc.com>
On Fri, 4 Jul 2003 14:11, Tom Sightler wrote:
> On Thu, 2003-07-03 at 22:29, Con Kolivas wrote:
> > Ah yes I believe I know this issue. The problem is the parent spinning
> > madly waiting for the child and it is the parent that starves the child.
> > While this is not a fix, if you can reproduce the problem can you try
> > changing CHILD_PENALTY in kernel/sched.c from 50 to 100 and see if that
> > makes the problem go away? I mentioned this hidden in a thread a while
> > ago, and am trying to get a reasonable fix.
>
> Well, perhaps I spoke too soon about this particular issues. I have
> just compiled 2.5.74-mm1 and it seems to be much better behaved that my
> previous kernel (2.5.72-mm2). I can no longer reproduce the issue with
> this new kernel but the problem is easily reproducible with my older
> kernel. Does 2.5.74-mm1 have a recent version of your patches (I know
> it has some variation of your patches but you've been cracking them out
> pretty quick lately). I've run testing with my horror cases of
> Crossover Plugin and multiple Crossover Office applications running
> simultaneously and all programs seem responsive, these cases caused all
> kinds of audio skipping and pauses on the system before.
>
> I'm still running some other tests that seem to be showing some
> strangeness but I need to do some more test on both kernels before I
> really reports them.
>
> Thanks for your hard work on these issues, for my workload things seem
> to be getting quite a bit better.
Heh well that's nice. The last patch posted on my site (
kernel.kolivas.org/2.5 ) is the same as in -mm1. There is no newer patch yet,
but I've got some changes coming to apply on top pretty soon. Hopefully these
will address your "strangeness". :)
Con
next prev parent reply other threads:[~2003-07-04 4:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 16:36 2.5.74-mm1 and Con Kolivas' CPU scheduler work ismail (cartman) donmez
2003-07-03 23:49 ` Con Kolivas
2003-07-04 2:09 ` Tom Sightler
2003-07-04 2:29 ` Con Kolivas
2003-07-04 4:11 ` Tom Sightler
2003-07-04 4:25 ` Con Kolivas [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-07-03 16:25 ismail (cartman) donmez
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=200307041425.29828.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=kde@myrealbox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ttsig@tuxyturvy.com \
/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.