From: Anton Blanchard <anton@samba.org>
To: Rick Lindsley <ricklind@us.ibm.com>
Cc: piggin@cyberone.com.au, akpm@osdl.org,
linux-kernel@vger.kernel.org, mjbligh@us.ibm.com,
dvhltc@us.ibm.com
Subject: Re: [PATCH] Load balancing problem in 2.6.2-mm1
Date: Fri, 6 Feb 2004 21:30:10 +1100 [thread overview]
Message-ID: <20040206103010.GI19011@krispykreme> (raw)
In-Reply-To: <200402060924.i169OWx30517@owlet.beaverton.ibm.com>
Hi,
> This patch allows for this_load to set max_load, which if I understand
> the logic properly is correct. It then adds a check to imbalance to make
> sure a negative number hasn't been coerced into a large positive number.
> With this patch applied, the algorithm is *much* more conservative ...
> maybe *too* conservative but that's for another round of testing ...
Good stuff, I just gave the patch a spin and things seem a little
calmer. However Im still seeing a lot of balancing going on within a
node.
Setup:
2 threads per cpu.
2 nodes of 16 threads each.
I ran a single "yes > /dev/null"
And it looks like that process is bouncing around the entire node.
Below is a 2 second average.
Anton
cpu user system idle cpu user system idle
node 0:
cpu0 2 0 99 cpu1 9 0 91
cpu2 1 0 99 cpu3 8 0 92
cpu4 3 0 97 cpu5 10 0 90
cpu6 2 0 98 cpu7 10 0 90
cpu8 2 0 98 cpu9 9 0 90
cpu10 3 0 96 cpu11 9 0 90
cpu12 2 0 98 cpu13 10 0 90
cpu14 2 1 97 cpu15 10 1 89
node 1:
cpu16 0 0 100 cpu17 0 0 100
cpu18 0 0 101 cpu19 0 0 100
cpu20 0 0 100 cpu21 0 0 101
cpu22 0 0 101 cpu23 0 0 100
cpu24 0 0 100 cpu25 0 0 100
cpu26 0 0 100 cpu27 0 0 100
cpu28 0 0 101 cpu29 0 0 100
cpu30 0 0 100 cpu31 0 0 100
next prev parent reply other threads:[~2004-02-06 10:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 9:24 [PATCH] Load balancing problem in 2.6.2-mm1 Rick Lindsley
2004-02-06 9:38 ` Nick Piggin
2004-02-06 18:13 ` Rick Lindsley
2004-02-06 21:57 ` Nick Piggin
2004-02-06 22:30 ` Rick Lindsley
2004-02-06 22:40 ` Nick Piggin
2004-02-06 22:49 ` Rick Lindsley
2004-02-06 23:08 ` Nick Piggin
2004-02-06 10:30 ` Anton Blanchard [this message]
2004-02-06 18:15 ` Rick Lindsley
2004-02-06 18:39 ` Martin J. Bligh
2004-02-06 22:02 ` Nick Piggin
2004-02-06 22:34 ` Rick Lindsley
2004-02-06 22:48 ` Nick Piggin
2004-02-06 22:42 ` Martin J. Bligh
2004-02-06 22:53 ` Nick Piggin
2004-02-06 23:11 ` Rick Lindsley
2004-02-06 23:20 ` Nick Piggin
2004-02-06 23:33 ` Martin J. Bligh
2004-02-06 23:41 ` Nick Piggin
2004-02-06 23:47 ` Martin J. Bligh
2004-02-07 0:11 ` Nick Piggin
2004-02-07 0:25 ` Martin J. Bligh
2004-02-07 0:31 ` Nick Piggin
2004-02-07 9:50 ` Anton Blanchard
2004-02-08 0:40 ` Rick Lindsley
2004-02-08 1:12 ` Anton Blanchard
2004-02-08 1:21 ` Nick Piggin
2004-02-08 1:41 ` Anton Blanchard
2004-02-08 3:20 ` Nick Piggin
2004-02-08 3:57 ` Anton Blanchard
2004-02-08 4:05 ` Nick Piggin
2004-02-08 12:14 ` Anton Blanchard
2004-02-08 1:22 ` Anton Blanchard
2004-02-09 16:37 ` Timothy Miller
2004-02-09 16:43 ` Martin J. Bligh
2004-02-06 18:33 ` Martin J. Bligh
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=20040206103010.GI19011@krispykreme \
--to=anton@samba.org \
--cc=akpm@osdl.org \
--cc=dvhltc@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjbligh@us.ibm.com \
--cc=piggin@cyberone.com.au \
--cc=ricklind@us.ibm.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