From: Michael Gerdau <mgd@technosis.de>
To: ck@vds.kolivas.org
Cc: Con Kolivas <kernel@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 10:02:07 +0200 [thread overview]
Message-ID: <200704221002.21289.mgd@technosis.de> (raw)
In-Reply-To: <200704221441.48897.kernel@kolivas.org>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
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 ?
Best wishes,
Michael
--
Technosis GmbH, Geschäftsführer: Michael Gerdau, Tobias Dittmar
Sitz Hamburg; HRB 89145 Amtsgericht Hamburg
Vote against SPAM - see http://www.politik-digital.de/spam/
Michael Gerdau email: mgd@technosis.de
GPG-keys available on request or at public keyserver
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-04-22 8:02 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 ` Michael Gerdau [this message]
2007-04-22 11:09 ` [ck] " Con Kolivas
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=200704221002.21289.mgd@technosis.de \
--to=mgd@technosis.de \
--cc=a1426z@gawab.com \
--cc=billh@gnuppy.monkey.org \
--cc=ck@vds.kolivas.org \
--cc=efault@gmx.de \
--cc=gene.heskett@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--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