Subject: Re: VolanoMark regression with 2.6.27-rc1
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
In-Reply-To: <Pine.LNX.4.64.0808011311360.20052@blonde.site>
References: <1217474425.25608.150.camel@ymzhang>
	 <Pine.LNX.4.64.0808011311360.20052@blonde.site>
Content-Type: text/plain
Date: Mon, 04 Aug 2008 08:54:04 +0800
Message-Id: <1217811244.25608.175.camel@ymzhang>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1354
Lines: 34


On Fri, 2008-08-01 at 13:25 +0100, Hugh Dickins wrote:
> On Thu, 31 Jul 2008, Zhang, Yanmin wrote:
> > 
> > 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...
> ....
> > BTW, sysbench+mysql(oltp readonly) has about 15% regression,
> > but git bisect looks crazy again.
> 
> I'm no git expert, but didn't see anyone else comment on this:
> you need to trust git more, it's like the Tour de France,
> occasionally venturing into other countries for a little while.
> 
> Work which got merged into Linus's 2.6.26-git for 2.6.27-rc1 may
> well have been developed on a 2.6.26-rcN base in someone else's
> tree, and so the bisection may take you back there.
> 
> I think this is getting commoner now, since Linus spoke out
> against rebasing: bisecting a net issue took me back to rc6-git
> and rc4-git, but did end up at the right commit.
Sometimes, git bisect could locate the culprit, but didn't this time.
I'm used to keep quiet when it's good but complain to make noisy when
something is wrong. :)

Thanks,
Yanmin


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/