[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1217489463.25608.157.camel@ymzhang>
Date: Thu, 31 Jul 2008 15:31:03 +0800
From: "Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: VolanoMark regression with 2.6.27-rc1
On Thu, 2008-07-31 at 11:20 +0800, Zhang, Yanmin wrote:
> Ingo,
>
> volanoMark has regression with 2.6.27-rc1.
> 1) 70% on 16-core tigerton;
> 2) 18% on a new multi-core+HT mahcine;
>
> I tried to use git bisect to locate the root cause, but git bisect always went
> back to 2.6.26. Then, I used my mechanical bisect script linearly to locate below commit:
>
> commit 82638844d9a8581bbf33201cc209a14876eca167
> Merge: 9982fbf... 63cf13b...
> Author: Ingo Molnar <mingo@...e.hu>
> Date: Wed Jul 16 00:29:07 2008 +0200
>
> Merge branch 'linus' into cpus4096
>
> Conflicts:
>
> arch/x86/xen/smp.c
> kernel/sched_rt.c
> net/iucv/iucv.c
>
> Signed-off-by: Ingo Molnar <mingo@...e.hu>
>
>
>
> But if I use 'git show 82638844d9a8581bbf33201cc209a14876eca167', it looks like I could only
> get a part of the patch. If I use web to acces the commit, I could get a big patch. As it's
> a merge, what're commit numbers of the subpatches?
>
>
> BTW, sysbench+mysql(oltp readonly) has about 15% regression, but git bisect looks crazy again.
Oh, it looks like they are the old issues in 2.6.26-rc1 and the 2 patches were reverted before 2.6.26.
New patches are merged into 2.6.27-rc1, but the issues are still not resolved clearly.
http://www.uwsg.iu.edu/hypermail/linux/kernel/0805.2/1148.html.
yanmin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists