From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Paul Turner <pjt@google.com>,
Arjan Van De Ven <arjan@linux.intel.com>,
Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: Re: [rfc][patch] select_idle_sibling() inducing bouncing on westmere
Date: Sun, 27 May 2012 13:02:25 +0200 [thread overview]
Message-ID: <1338116545.27146.22.camel@marge.simpson.net> (raw)
In-Reply-To: <1338110259.7678.77.camel@marge.simpson.net>
BTW, there's something pretty darn strange going on in westmere land.
Take a peek at this, note how upset it gets at large size, and how it
then can't keep up with crusty old Q6600. Numbers are a bit erratic,
but you'll see it. Identical kernels, not that kernel matters.
Q6600
marge:/usr/local/tmp/lmbench3 # !968
for m in 16K 32K 64K 128K 256K 512K 1M 2M 4M 8M; do bin/x86_64-linux-gnu/bw_tcp -P 1 -N 3 -m $m localhost; done
select_idle_sibling() !select_idle_sibling()
0.016384 1655.83 MB/sec 1628.55 MB/sec
0.032768 1816.77 MB/sec 2086.87 MB/sec
0.065536 3148.80 MB/sec 2117.82 MB/sec
0.131072 2356.40 MB/sec 1493.96 MB/sec
0.262144 2827.00 MB/sec 1908.48 MB/sec
0.524288 3301.68 MB/sec 1908.48 MB/sec
1.048576 3359.03 MB/sec 1553.58 MB/sec
2.097152 3143.11 MB/sec 2259.11 MB/sec
4.194304 3020.53 MB/sec 1949.93 MB/sec
8.388608 2823.97 MB/sec 1868.70 MB/sec
E5620
rtbox:/usr/local/tmp/lmbench3 # !877
for m in 16K 32K 64K 128K 256K 512K 1M 2M 4M 8M; do bin/x86_64-linux-gnu/bw_tcp -P 1 -N 3 -m $m localhost; done
select_idle_sibling() !select_idle_sibling()
0.016384 3461.28 MB/sec 2687.59 MB/sec
0.032768 4400.77 MB/sec 2939.77 MB/sec
0.065536 4517.30 MB/sec 2738.92 MB/sec
0.131072 3441.09 MB/sec 1894.25 MB/sec
0.262144 3919.65 MB/sec 2479.68 MB/sec
0.524288 1232.65 MB/sec 2341.83 MB/sec
1.048576 1230.15 MB/sec 2398.64 MB/sec
2.097152 1875.09 MB/sec 1591.16 MB/sec
4.194304 1382.21 MB/sec 1791.67 MB/sec
8.388608 1406.07 MB/sec 1078.92 MB/sec
next prev parent reply other threads:[~2012-05-27 11:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 11:04 Mike Galbraith
2012-05-24 13:17 ` Peter Zijlstra
2012-05-24 13:20 ` Peter Zijlstra
2012-05-25 6:14 ` Mike Galbraith
2012-05-26 6:37 ` Mike Galbraith
2012-05-26 7:29 ` Peter Zijlstra
2012-05-26 8:27 ` Mike Galbraith
2012-05-27 9:17 ` Mike Galbraith
2012-05-27 11:02 ` Mike Galbraith [this message]
2012-05-27 11:12 ` Mike Galbraith
2012-05-27 14:11 ` Arjan van de Ven
2012-05-27 14:29 ` Mike Galbraith
2012-05-27 14:32 ` Mike Galbraith
2012-05-29 18:58 ` Andreas Herrmann
2012-05-25 6:08 ` Mike Galbraith
2012-05-25 8:06 ` Mike Galbraith
2012-06-05 14:30 ` Mike Galbraith
2012-06-11 16:57 ` [patch v3] sched: fix select_idle_sibling() induced bouncing Mike Galbraith
2012-06-11 17:22 ` Peter Zijlstra
2012-06-11 17:55 ` Mike Galbraith
2012-06-11 18:53 ` Suresh Siddha
2012-06-12 3:18 ` Mike Galbraith
2012-06-20 10:48 ` [tip:sched/core] sched: Improve scalability via 'CPU buddies', which withstand random perturbations tip-bot for Mike Galbraith
2012-07-24 14:18 ` tip-bot for Mike Galbraith
2012-06-19 8:47 ` [patch v3] sched: fix select_idle_sibling() induced bouncing Paul Turner
2012-06-06 10:17 ` [rfc][patch] select_idle_sibling() inducing bouncing on westmere Mike Galbraith
2012-06-06 10:38 ` Mike Galbraith
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=1338116545.27146.22.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=andreas.herrmann3@amd.com \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=suresh.b.siddha@intel.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
all inboxes | Powered by JetHome®