Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757532AbYHDFIS (ORCPT ); Mon, 4 Aug 2008 01:08:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751626AbYHDFIJ (ORCPT ); Mon, 4 Aug 2008 01:08:09 -0400 Received: from mga06.intel.com ([134.134.136.21]:5247 "EHLO orsmga101.jf.intel.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751296AbYHDFII (ORCPT ); Mon, 4 Aug 2008 01:08:08 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.31,302,1215414000"; d="scan'208";a="322800363" Subject: Re: VolanoMark regression with 2.6.27-rc1 From: "Zhang, Yanmin" To: Dhaval Giani Cc: Peter Zijlstra , Ingo Molnar , LKML , Srivatsa Vaddagiri , Aneesh Kumar KV , Balbir Singh In-Reply-To: <20080801051407.GA5232@linux.vnet.ibm.com> References: <1217474425.25608.150.camel@ymzhang> <1217489463.25608.157.camel@ymzhang> <1217489949.8157.78.camel@twins> <1217490560.25608.168.camel@ymzhang> <1217551154.25608.169.camel@ymzhang> <20080801051407.GA5232@linux.vnet.ibm.com> Content-Type: text/plain Date: Mon, 04 Aug 2008 13:04:38 +0800 Message-Id: <1217826278.25608.198.camel@ymzhang> Mime-Version: 1.0 X-Mailer: Evolution 2.21.5 (2.21.5-2.fc9) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2875 Lines: 69 On Fri, 2008-08-01 at 10:44 +0530, Dhaval Giani wrote: > On Fri, Aug 01, 2008 at 08:39:14AM +0800, Zhang, Yanmin wrote: > > > > On Thu, 2008-07-31 at 15:49 +0800, Zhang, Yanmin wrote: > > > On Thu, 2008-07-31 at 09:39 +0200, Peter Zijlstra wrote: > > > > On Thu, 2008-07-31 at 15:31 +0800, Zhang, Yanmin wrote: > > > > > On Thu, 2008-07-31 at 11:20 +0800, Zhang, Yanmin wrote: > > > > > > Ingo, > > > > > > > > > > > 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. > > > > > > > > The new smp-group stuff doesn't remotely look like what was in .26 > > > > > > > > Also, on my quad (admittedly smaller than your machines) both volano and > > > > sysbench didn't regress anymore - where they clearly did with the code > > > > reverted from .26. > > > The regression I reported exists on: > > > 1) 8-core+HT(totally 16 logical processor) tulsa: 40% regression with volano, 8% with oltp; > > > 2) 8-core+HT Montvale Itanium: 9% regression with volano; 8% with oltp; > > > 3) 16-core tigerton: %70 with volano, %18 with oltp; > > > 4) 8-core stoakley: %15 with oltp, testing failed with volanoMark. > > > > > > So the issues are popular on different architectures. > > I know kernel needs the features and it might not be a good idea to reject them over and over again. > > I will collect more data on tigerton and try to optimize it. > > Hi Yanmin, > > Would it be possible for you to switch of the group scheduling feature > and see if the regression still exists. In all our testing, we did not > see a regression. I would like to eliminate it from your testing as > well. I tested with CONFIG_GROUP_SCHED=n. To test faster, I simplified the benchmark parameter. volanoMark: kernel | result ---------------------------------------------------------- 2.6.27-rc1_group | 205901 ---------------------------------------------------------- 2.6.27-rc1_nogroup | 303377 ---------------------------------------------------------- 2.6.26_group | 529388 sysbench+mysql(readonly oltp): kernel | result ----------------------------------------------------------- 2.6.27-rc1_group | 560636 ----------------------------------------------------------- 2.6.27-rc1_nogroup | 604937 ----------------------------------------------------------- 2.6.26_group | 627384 > > The option to switch off would be CONFIG_GROUP_SCHED, that should disable > all the group scheduling features. > > Thanks, -- 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/