From: Mike Galbraith <efault@gmx.de>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: hackbench regression with kernel 2.6.32-rc1
Date: Mon, 12 Oct 2009 10:05:31 +0200 [thread overview]
Message-ID: <1255334731.7282.3.camel@marge.simson.net> (raw)
In-Reply-To: <1255331120.3684.43.camel@ymzhang>
On Mon, 2009-10-12 at 15:05 +0800, Zhang, Yanmin wrote:
> The good news is only tbench has about 6% regression on Nehalem machines.
> Other regressions such like hackbench/aim7/volanoMark is not clear/big on
> Nehalem. But reverting the original 2 patches don't fix the tbench regression
> on Nehalem machines.
Could be NO_NEXT_BUDDY. NEXT_BUDDY is pretty important for scaling.
-Mike
next prev parent reply other threads:[~2009-10-12 8:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 9:19 hackbench regression with kernel 2.6.32-rc1 Zhang, Yanmin
2009-10-09 10:43 ` Peter Zijlstra
2009-10-12 7:05 ` Zhang, Yanmin
2009-10-12 8:05 ` Mike Galbraith [this message]
2009-10-12 14:21 ` Peter Zijlstra
2009-10-12 14:33 ` Mike Galbraith
2009-10-13 3:12 ` Zhang, Yanmin
2009-10-13 9:39 ` Mike Galbraith
2009-10-13 11:08 ` Mike Galbraith
2009-10-16 11:06 ` Mike Galbraith
2009-10-27 8:03 ` Zhang, Yanmin
2009-10-27 14:42 ` Mike Galbraith
2009-10-28 9:29 ` Zhang, Yanmin
2009-10-28 14:22 ` Mike Galbraith
2009-10-29 0:50 ` Zhang, Yanmin
2009-10-29 5:46 ` Mike Galbraith
2009-10-29 6:26 ` Zhang, Yanmin
2009-10-29 9:14 ` [patch] " Mike Galbraith
2009-10-30 2:02 ` Zhang, Yanmin
2009-10-14 13:13 ` [tip:sched/urgent] sched: Do less agressive buddy clearing tip-bot for Peter Zijlstra
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=1255334731.7282.3.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.