linux-kernel - Re: tbench regression with 2.6.33-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1263288024.3598.52.camel@minggr.sh.intel.com>
Date:	Tue, 12 Jan 2010 17:20:24 +0800
From:	Lin Ming <ming.m.lin@...el.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Mike Galbraith <efault@....de>, "mingo@...e.hu" <mingo@...e.hu>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
Subject: Re: tbench regression with 2.6.33-rc1

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

Download attachment "sched-2.6.33-rc1.patch.tar.bz2" of type "application/x-bzip-compressed-tar" (213 bytes)