public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lin Ming <ming.m.lin@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mike Galbraith <efault@gmx.de>, "mingo@elte.hu" <mingo@elte.hu>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Subject: Re: tbench regression with 2.6.33-rc1
Date: Tue, 12 Jan 2010 17:20:24 +0800	[thread overview]
Message-ID: <1263288024.3598.52.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <1263286449.4244.101.camel@laptop>

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

On Tue, 2010-01-12 at 16:54 +0800, Peter Zijlstra wrote:
> On Tue, 2010-01-12 at 09:09 +0800, Lin Ming wrote:
> > I test this patch applied to 2.6.33-rc3, but no help on tbench
> > regression. 
> 
> How stable is this regression on your machines? That is, can you bisect
> it? Me and Mike seem to have no luck bisecting it, ending up at totally
> unrelated patches and the like :/

I tried bisect weeks ago, but the bisect result is not stable.

Then I tried another way to reproduce this regression.
I picked up most scheduler related patches that merged into 2.6.33-rc1,
and applied them to 2.6.32, then the ~4% regression was reproduced.

But again, the bisect result among these scheduler related patches was
not stable either. The regression seems not caused by one single patch,
but the accumulation of some patches.

You may try the attached scheduler patches to reproduce the regression.

git checkout v2.6.32
git am sched-2.6.33-rc1.patch

Lin Ming




[-- Attachment #2: sched-2.6.33-rc1.patch.tar.bz2 --]
[-- Type: application/x-bzip-compressed-tar, Size: 213 bytes --]

      reply	other threads:[~2010-01-12  9:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-25 11:11 tbench regression with 2.6.33-rc1 Lin Ming
2009-12-27  8:32 ` Mike Galbraith
2009-12-27  8:59   ` Peter Zijlstra
2009-12-27  9:41     ` Mike Galbraith
2009-12-27 10:11       ` Peter Zijlstra
2010-01-02  3:56         ` Frederic Weisbecker
2009-12-29  2:09   ` Lin Ming
2009-12-29  5:24     ` Mike Galbraith
2009-12-29  5:19       ` Lin Ming
2009-12-29  5:49         ` Mike Galbraith
2010-01-06  6:01           ` Mike Galbraith
2010-01-06  5:55             ` Lin Ming
2010-01-06  6:52               ` Lin Ming
2010-01-06  7:44                 ` Mike Galbraith
2010-01-11 12:08 ` Peter Zijlstra
2010-01-11 16:16   ` Mike Galbraith
2010-01-12  1:09     ` Lin Ming
2010-01-12  2:33       ` Mike Galbraith
2010-01-12  3:13         ` Lin Ming
2010-01-12  4:14           ` Mike Galbraith
2010-01-12  8:54       ` Peter Zijlstra
2010-01-12  9:20         ` Lin Ming [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=1263288024.3598.52.camel@minggr.sh.intel.com \
    --to=ming.m.lin@intel.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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