From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Srivatsa Vaddagiri <vatsa@in.ibm.com>
Subject: Re: volanoMark regression with kernel 2.6.26-rc1
Date: Thu, 8 May 2008 11:04:31 +0530 [thread overview]
Message-ID: <20080508053431.GB32729@linux.vnet.ibm.com> (raw)
In-Reply-To: <1210224012.3453.105.camel@ymzhang>
On Thu, May 08, 2008 at 01:20:12PM +0800, Zhang, Yanmin wrote:
>
> On Wed, 2008-05-07 at 19:34 +0200, Peter Zijlstra wrote:
> > On Wed, 2008-05-07 at 11:17 +0200, Ingo Molnar wrote:
> > > * Zhang, Yanmin <yanmin_zhang@linux.intel.com> 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.
> > >
> > > thanks Yanmin, i've queued up your patch that reverts this change.
> >
> > Is this really needed now that GROUP_SCHED defaults to 'n' ?
> >
> > Yanmin, this is with GROUP_SCHED=y, right or is this without?
> With GROUP_SCHED=y.
>
> I remember a similiar patch was merged into 2.6.25-rc1 and I found the similiar volanoMark
> regression, then you reverted it. Why to add it back to 2.6.26-rc1?
>
The implementation has been changed extensively. As of now, without
proper load balancing, group scheduling is not yet fully fair, but such a
performance regression is serious, and we need to figure out why the
regression is taking place.
--
regards,
Dhaval
next prev parent reply other threads:[~2008-05-08 5: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
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 [this message]
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=20080508053431.GB32729@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@in.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox