From: Peter Williams <pwil3058@bigpond.net.au>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] CFS scheduler, -v12
Date: Fri, 18 May 2007 09:45:01 +1000 [thread overview]
Message-ID: <464CE8FD.4070205@bigpond.net.au> (raw)
In-Reply-To: <20070516063625.GA9058@elte.hu>
Ingo Molnar wrote:
> * Peter Williams <pwil3058@bigpond.net.au> wrote:
>
>> Load balancing appears to be badly broken in this version. When I
>> started 4 hard spinners on my 2 CPU machine one ended up on one CPU
>> and the other 3 on the other CPU and they stayed there.
>
> could you try to debug this a bit more?
I've now done this test on a number of kernels: 2.6.21 and 2.6.22-rc1
with and without CFS; and the problem is always present. It's not
"nice" related as the all four tasks are run at nice == 0.
It's possible that this problem has been in the kernel for a while with
out being noticed as, even with totally random allocation of tasks to
CPUs without any (attempt to balance), there's a quite high probability
of the desirable 2/2 split occurring. So one needs to repeat the test
several times to have reasonable assurance that the problem is not
present. I.e. this has the characteristics of an intermittent bug with
all the debugging problems that introduces.
The probabilities for the 3 split possibilities for random allocation are:
2/2 (the desired outcome) is 3/8 likely,
1/3 is 4/8 likely, and
0/4 is 1/8 likely.
I'm pretty sure that this problem wasn't present when smpnice went into
the kernel which is the last time I did a lot of load balance testing.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2007-05-17 23:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 15:38 [patch] CFS scheduler, -v12 Ingo Molnar
2007-05-16 2:04 ` Peter Williams
2007-05-16 8:08 ` Ingo Molnar
2007-05-16 23:42 ` Peter Williams
[not found] ` <20070516063625.GA9058@elte.hu>
2007-05-17 23:45 ` Peter Williams [this message]
[not found] ` <20070518071325.GB28702@elte.hu>
2007-05-18 13:11 ` Peter Williams
2007-05-18 13:26 ` Peter Williams
2007-05-19 13:27 ` Dmitry Adamushko
2007-05-20 1:41 ` Peter Williams
2007-05-21 8:29 ` William Lee Irwin III
2007-05-21 8:57 ` Ingo Molnar
2007-05-21 12:08 ` William Lee Irwin III
2007-05-22 16:48 ` Chris Friesen
2007-05-22 20:15 ` Ingo Molnar
2007-05-22 20:49 ` Chris Friesen
2007-05-21 15:25 ` Dmitry Adamushko
2007-05-21 23:51 ` Peter Williams
2007-05-22 4:47 ` Peter Williams
2007-05-22 12:03 ` Peter Williams
2007-05-24 7:43 ` Peter Williams
2007-05-24 16:45 ` Siddha, Suresh B
2007-05-24 23:23 ` Peter Williams
2007-05-29 20:45 ` Siddha, Suresh B
2007-05-29 23:54 ` Peter Williams
2007-05-30 0:50 ` Siddha, Suresh B
2007-05-30 2:18 ` Peter Williams
2007-05-30 4:42 ` Siddha, Suresh B
2007-05-30 6:28 ` Peter Williams
2007-05-31 1:49 ` Peter Williams
2007-05-22 11:52 ` Dmitry Adamushko
2007-05-23 0:10 ` Peter Williams
2007-05-18 0:18 ` Bill Huey
2007-05-18 1:01 ` Bill Huey
2007-05-18 4:13 ` William Lee Irwin III
2007-05-18 7:31 ` 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=464CE8FD.4070205@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--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