From: Ingo Molnar <mingo@elte.hu>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Mike Galbraith <efault@gmx.de>
Subject: Re: specjbb2005 and aim7 regression with 2.6.32-rc kernels
Date: Fri, 6 Nov 2009 09:04:18 +0100 [thread overview]
Message-ID: <20091106080418.GB28227@elte.hu> (raw)
In-Reply-To: <1257493130.16282.109.camel@ymzhang>
* Zhang, Yanmin <yanmin_zhang@linux.intel.com> wrote:
> Comparing with 2.6.31, specjbb2005 and aim7 have some regressions with
> 2.6.32-rc kernels on core2 machines.
>
> 1) On 4*4 core tigerton: specjbb2005 has about 5% regression.
> 2) On 2*4 stoakley: aim7 has about 5% regression.
>
> On Nehalem, specjbb2005 has about 2%~8% improvement instead of
> regression.
>
> aim7 has much dependency on schedule patameters, such like
> sched_latency_ns, sched_min_granularity_ns, and
> sched_wakeup_granularity_ns. 2.6.32-rc kernel decreases these
> parameter values. I restore them and retest aim7 on stoakley. aim7
> regression becomes about 2% and specjbb2005 regression also becomes
> 2%. But on Nehalem, the improvement shrinks.
Which precise 2.6.32-rc commit have you tested?
Since v2.6.32-rc6 Linus's tree has this one too:
f685cea: sched: Strengthen buddies and mitigate buddy induced latencies
Which should improve things a bit. For 2.6.33 we have queued up these
two in -tip:
a1f84a3: sched: Check for an idle shared cache in select_task_rq_fair()
1b9508f: sched: Rate-limit newidle
If any of them fixes a performance regression we could still merge them
into 2.6.32 as well.
Ingo
next prev parent reply other threads:[~2009-11-06 8:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 7:38 specjbb2005 and aim7 regression with 2.6.32-rc kernels Zhang, Yanmin
2009-11-06 8:02 ` Mike Galbraith
2009-11-06 8:04 ` Ingo Molnar [this message]
2009-11-09 6:19 ` Zhang, Yanmin
2009-11-09 7:09 ` Mike Galbraith
2009-11-09 9:15 ` Peter Zijlstra
2009-11-09 9:44 ` Gautham R Shenoy
2009-11-09 9:57 ` Mike Galbraith
2009-11-09 9:55 ` 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=20091106080418.GB28227@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.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 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.