From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
Aneesh Kumar KV <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: volanoMark regression with kernel 2.6.26-rc1
Date: Wed, 7 May 2008 23:03:57 +0530 [thread overview]
Message-ID: <20080507173357.GA4424@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080506115207.GA24862@linux.vnet.ibm.com>
On Tue, May 06, 2008 at 05:22:07PM +0530, Dhaval Giani wrote:
> On Tue, May 06, 2008 at 10:06:30AM +0800, Zhang, Yanmin wrote:
> > Comparing with 2.6.25, volanoMark has big regression with kernel 2.6.26-rc1.
> > It's about 50% on my 8-core stoakley, 16-core tigerton, and Itanium Montecito.
> >
> > With bisect, I located below patch.
> >
> > 18d95a2832c1392a2d63227a7a6d433cb9f2037e is first bad commit
> > commit 18d95a2832c1392a2d63227a7a6d433cb9f2037e
> > Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Date: Sat Apr 19 19:45:00 2008 +0200
> >
> > sched: fair-group: SMP-nice for group scheduling
> >
> > Implement SMP nice support for the full group hierarchy.
> >
> > If I reverse the patch with resolving some conflictions, volanoMark result could
> > be restored completely.
> >
>
> ok, that's bad. Let's get vatsa and Ingo also involved.
>
Just to confirm, do you still have a performance regression with
!group_sched?
--
regards,
Dhaval
next prev parent reply other threads:[~2008-05-07 17:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 2:06 volanoMark regression with kernel 2.6.26-rc1 Zhang, Yanmin
2008-05-06 5:41 ` Zhang, Yanmin
2008-05-06 11:52 ` Dhaval Giani
2008-05-07 17:33 ` Dhaval Giani [this message]
2008-05-08 5:18 ` Zhang, Yanmin
2008-05-08 5:32 ` Dhaval Giani
2008-05-08 5:40 ` Dhaval Giani
2008-05-08 5:53 ` Zhang, Yanmin
2008-05-08 6:04 ` Dhaval Giani
2008-05-08 6:11 ` Srivatsa Vaddagiri
2008-05-09 15:52 ` Srivatsa Vaddagiri
2008-05-09 15:54 ` Srivatsa Vaddagiri
2008-05-12 1:39 ` Zhang, Yanmin
2008-05-12 2:04 ` Dhaval Giani
2008-05-12 2:37 ` Srivatsa Vaddagiri
2008-05-12 3:33 ` Zhang, Yanmin
2008-05-12 4:52 ` Srivatsa Vaddagiri
2008-05-12 5:02 ` Zhang, Yanmin
2008-05-12 5:43 ` Zhang, Yanmin
2008-05-12 9:04 ` Mike Galbraith
2008-05-12 9:20 ` Peter Zijlstra
2008-05-14 9:22 ` Zhang, Yanmin
2008-05-14 13:44 ` Srivatsa Vaddagiri
2008-05-14 14:50 ` Mike Galbraith
2008-05-14 15:12 ` Peter Zijlstra
2008-05-15 8:20 ` Srivatsa Vaddagiri
2008-05-15 8:41 ` Peter Zijlstra
2008-05-15 17:10 ` Srivatsa Vaddagiri
2008-05-07 7:04 ` Andrew Morton
2008-05-07 9:17 ` Ingo Molnar
2008-05-07 9:33 ` Zhang, Yanmin
2008-05-07 17:34 ` Peter Zijlstra
2008-05-07 18:58 ` Peter Zijlstra
2008-05-08 6:07 ` Zhang, Yanmin
2008-05-08 5:20 ` Zhang, Yanmin
2008-05-08 5:34 ` Dhaval Giani
2008-05-08 6:43 ` Peter Zijlstra
2008-05-07 17:42 ` Dhaval Giani
2008-05-08 5:21 ` Zhang, Yanmin
2008-05-08 5:39 ` Dhaval Giani
2008-05-08 6:03 ` Zhang, Yanmin
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=20080507173357.GA4424@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.com \
--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.