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 12:29:06 +1000 [thread overview]
Message-ID: <200307041229.06238.kernel@kolivas.org> (raw)
In-Reply-To: <1057284551.1725.8.camel@iso-8590-lx.zeusinc.com>
On Fri, 4 Jul 2003 12:09, Tom Sightler wrote:
> On Thu, 2003-07-03 at 19:49, Con Kolivas wrote:
> > On Fri, 4 Jul 2003 02:36, ismail (cartman) donmez wrote:
> > > Hi,
> > >
> > > With Con Kolivas' cpu patch I got many slow downs. When I try to run
> > > CodeWeaver's CrossOver office box gets unresponsive at least for a one
> > > minute. While starting KDE ( when splash screen is running ) mouse gets
> > > too sluggish.
> >
> > While your wm starting if your mouse is sluggish it is probably not a big
> > problem, and it is part of something I'm already working on. The
> > codeweavers problem is impressive though; I don't have codeweavers and
> > have not seen anything like it. To get a full picture it would be helpful
> > if you could run top as root say reniced to -13 just so it doesn't miss
> > anything, and then start codeweavers, watch top and tell me what is
> > spinning away hogging the cpu.
>
> My guess is that he's seeing the same issue that I reported a few weeks
> ago with Crossover plugin. That report generated a fairly long thread
> and a lot of patches and testing, but little actual progress. Basically
> wine seems to have multiple threads and a client/server architecture and
> seems constantly spin on a pipe passing info back and forth to each
> other. It seems one thread gets all the attention and starves the
> others although the others are critical for the main process to actually
> make progress.
>
> I've been wanting to do some testing with your patches so I'll give them
> a spin tonight and see how this acts.
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.
Con
next prev parent reply other threads:[~2003-07-04 2:17 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 [this message]
2003-07-04 4:11 ` Tom Sightler
2003-07-04 4:25 ` Con Kolivas
-- 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=200307041229.06238.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox