From: Manfred Spraul <manfred@colorfullife.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: cross-cpu balancing with the new scheduler
Date: Sun, 13 Jan 2002 18:01:40 +0100 [thread overview]
Message-ID: <3C41BD74.28F6707A@colorfullife.com> (raw)
Is it possible that the inter-cpu balancing is broken in 2.5.2-pre11?
eatcpu is a simple cpu hog ("for(;;);"). Dual CPU i386.
$nice -19 ./eatcpu&;
<wait>
$nice -19 ./eatcpu&;
<wait>
$./eatcpu&.
IMHO it should be
* both niced process run on one cpu.
* the non-niced process runs with a 100% timeslice.
But it's the other way around:
One niced process runs with 100%. The non-niced process with 50%, and
the second niced process with 50%.
--
Manfred
next reply other threads:[~2002-01-13 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-13 17:01 Manfred Spraul [this message]
2002-01-14 2:19 ` cross-cpu balancing with the new scheduler Rusty Russell
2002-01-14 2:49 ` Davide Libenzi
2002-01-14 4:37 ` Rusty Russell
2002-01-14 15:39 ` Manfred Spraul
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=3C41BD74.28F6707A@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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