From: Con Kolivas <kernel@kolivas.org>
To: Michael Gerdau <mgd@technosis.de>
Cc: ck@vds.kolivas.org,
linux kernel mailing list <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Mike Galbraith <efault@gmx.de>,
Al Boldi <a1426z@gawab.com>,
Peter Williams <pwil3058@bigpond.net.au>,
Nick Piggin <npiggin@suse.de>, Matt Mackall <mpm@selenic.com>,
Bill Huey <billh@gnuppy.monkey.org>,
William Lee Irwin III <wli@holomorphy.com>,
Willy Tarreau <w@1wt.eu>, Gene Heskett <gene.heskett@gmail.com>
Subject: Re: [ck] [ANNOUNCE] Staircase Deadline cpu scheduler version 0.45
Date: Sun, 22 Apr 2007 21:09:23 +1000 [thread overview]
Message-ID: <200704222109.24294.kernel@kolivas.org> (raw)
In-Reply-To: <200704221002.21289.mgd@technosis.de>
On Sunday 22 April 2007 18:02, Michael Gerdau wrote:
> Hi Con,
>
> I now have 2.6.21-rc7-sd-0.45 running on my Intel Core2 T7600 2.33
> machine and there is something I don't understand.
>
> For testing I have a Perl script that does some numbercrunching
> and runs a couple of hours.
>
> I have two scenarios
> a) start the job via loops in a shellscript
> b) start the job via a makefile (make -j 2)
> that I run in parallel.
>
> I watch the jobs via top and this is what I see:
> Job a) quickly gets about 100% (- 0-2) while job b) creates two
> perl jobs that both get 50% (- 0-2). I suppose it is expected
> behaviour that the single perl job created via a) gets same same
> share of the cpu as the two perl jobs created via b) together.
>
> However occasionally cpu drops to 33% for all three perl jobs
> while there is no other job visible in top (i.e. the sum drops
> from 200% to 100%). After some time this changes back to 100/50/50.
>
> How could this happen and would applying the other patch you
> mailed to Willy Tarreau help tracking that down ?
Thanks for report. That patch did not help Willy, and now you have confirmed
there still is an SMP balancing problem too where it doesn't seem to keep all
cpus busy. There's still a bug there in the smp balancing code and I'm
reviewing it madly trying to find it. If anyone else knows this balancing
code and is willing to help I'd be happy for feedback if they can see an
obvious error. Likely thing is the runqueue is not being weighted at all
despite being bust so the other runqueue doesn't try to take any tasks from
it.
--
-ck
prev parent reply other threads:[~2007-04-22 11:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 4:41 [ANNOUNCE] Staircase Deadline cpu scheduler version 0.45 Con Kolivas
2007-04-22 7:00 ` Willy Tarreau
2007-04-22 7:27 ` Con Kolivas
2007-04-22 7:31 ` Con Kolivas
2007-04-22 8:06 ` Willy Tarreau
2007-04-22 8:53 ` Con Kolivas
2007-04-22 9:14 ` Willy Tarreau
2007-04-22 9:53 ` Con Kolivas
2007-04-22 11:42 ` Con Kolivas
2007-04-22 12:18 ` [ck] " Con Kolivas
2007-04-22 13:07 ` Willy Tarreau
2007-04-22 13:27 ` Con Kolivas
2007-04-22 14:22 ` Willy Tarreau
2007-04-22 14:35 ` Con Kolivas
2007-04-23 7:02 ` Con Kolivas
2007-04-22 14:27 ` Michael Gerdau
2007-04-22 14:37 ` Con Kolivas
2007-04-22 8:02 ` [ck] " Michael Gerdau
2007-04-22 11:09 ` 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=200704222109.24294.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=a1426z@gawab.com \
--cc=billh@gnuppy.monkey.org \
--cc=ck@vds.kolivas.org \
--cc=efault@gmx.de \
--cc=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgd@technosis.de \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=npiggin@suse.de \
--cc=pwil3058@bigpond.net.au \
--cc=w@1wt.eu \
--cc=wli@holomorphy.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