From: Mike Galbraith <efault@gmx.de>
To: Lin Ming <ming.m.lin@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
lkml <linux-kernel@vger.kernel.org>,
"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Subject: Re: [RFC PATCH] sched: Pass affine target cpu into wake_affine
Date: Fri, 08 Jan 2010 04:34:29 +0100 [thread overview]
Message-ID: <1262921669.5601.25.camel@marge.simson.net> (raw)
In-Reply-To: <1262918331.3598.14.camel@minggr.sh.intel.com>
On Fri, 2010-01-08 at 10:38 +0800, Lin Ming wrote:
> On Thu, 2010-01-07 at 21:14 +0800, Mike Galbraith wrote:
> > Below is a complete retest. Mind testing my hacklet? I bet a nickle
> > it'll work at least as well as yours on your beefy boxen.
>
> I tested your hacklet on below 2 machines as before.
>
> Tigerton x86_64 machine: 16cpus(4P/4Cores), 40G mem
> IA64 machine: 32cpus(4P/4Cores/HT), 16G mem
>
> Test1: vmark regression fix patch + pass affine target
> Test2: this hacklet
>
> Compared with upstream 2.6.33-rc2,
> Test1: Tigerton +3%, IA64 +15%
> Test2: Tigerton +3%, IA64 +10%
>
> The test2 also improves on IA64, although not as good as test1.
Dang, I owe you a nickle. Thanks a bunch for giving it a go.
Interesting result. It's not really making much sense why you see a
peak gain, while I see peak loss. Radical behavior difference :-/
I think the ramp only (and harder) approach is safer, but we'll see.
-Mike
prev parent reply other threads:[~2010-01-08 3:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 9:03 Lin Ming
2010-01-04 9:25 ` Peter Zijlstra
2010-01-04 9:12 ` Lin Ming
2010-01-04 9:32 ` Peter Zijlstra
2010-01-04 10:59 ` Mike Galbraith
2010-01-04 11:07 ` Lin Ming
2010-01-05 2:48 ` Lin Ming
2010-01-05 3:44 ` Mike Galbraith
2010-01-05 6:43 ` Mike Galbraith
2010-01-05 11:49 ` Mike Galbraith
2010-01-07 8:45 ` Lin Ming
2010-01-07 9:15 ` Peter Zijlstra
2010-01-07 9:33 ` Mike Galbraith
2010-01-07 13:14 ` Mike Galbraith
2010-01-08 2:38 ` Lin Ming
2010-01-08 3:34 ` Mike Galbraith [this message]
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=1262921669.5601.25.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@intel.com \
--cc=peterz@infradead.org \
--cc=yanmin_zhang@linux.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
Powered by JetHome