From: Manfred Spraul <manfred@colorfullife.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: cross-cpu balancing with the new scheduler
Date: Mon, 14 Jan 2002 16:39:19 +0100 [thread overview]
Message-ID: <3C42FBA7.B1084B4D@colorfullife.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0201131842570.937-100000@blue1.dev.mcafeelabs.com>
Davide Libenzi wrote:
>
> I've a very simple phrase when QA is bugging me with these corner cases :
>
> "As Designed"
>
> It's much much better than adding code and "Return To QA" :-)
> I tried priority balancing in BMQS but i still prefer "As Designed" ...
>
Another test, now with 4 process (dual cpu):
#nice -n 19 ./eatcpu&
#nice -n 19 ./eatcpu&
#./eatcpu&
#nice -n -19 ./eatcpu&
And the top output:
<<<<<<
73 processes: 68 sleeping, 5 running, 0 zombie, 0 stopped
CPU0 states: 100.0% user, 0.0% system, 100.0% nice, 0.0% idle
CPU1 states: 98.0% user, 2.0% system, 33.0% nice, 0.0% idle
[snip]
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND
1163 root 39 19 396 396 324 R N 99.5 0.1 0:28 eatcpu
1164 root 39 19 396 396 324 R N 33.1 0.1 0:11 eatcpu
1165 root 39 0 396 396 324 R 33.1 0.1 0:07 eatcpu
1166 root 39 -19 396 396 324 R < 31.3 0.1 0:06 eatcpu
1168 manfred 1 0 980 976 768 R 2.7 0.2 0:00 top
[snip]
The niced process still has it's own cpu, and the "nice -19" process has
33% of the second cpu.
IMHO that's buggy. 4 running process, 1 on cpu0, 3 on cpu1.
--
Manfred
next prev parent reply other threads:[~2002-01-14 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-13 17:01 cross-cpu balancing with the new scheduler Manfred Spraul
2002-01-14 2:19 ` Rusty Russell
2002-01-14 2:49 ` Davide Libenzi
2002-01-14 4:37 ` Rusty Russell
2002-01-14 15:39 ` Manfred Spraul [this message]
2002-01-14 15:50 ` Davide Libenzi
2002-01-14 17:44 ` Ingo Molnar
2002-01-14 6:10 ` Anton Blanchard
2002-01-15 16:37 ` Ingo Molnar
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=3C42FBA7.B1084B4D@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
/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