From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933581Ab0JRX7S (ORCPT ); Mon, 18 Oct 2010 19:59:18 -0400 Received: from mga09.intel.com ([134.134.136.24]:36032 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933468Ab0JRX7Q (ORCPT ); Mon, 18 Oct 2010 19:59:16 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.57,347,1283756400"; d="scan'208";a="668607342" Subject: Re: [UnifiedV4 00/16] The Unified slab allocator (V4) From: "Alex,Shi" To: Christoph Lameter Cc: "Wu, Fengguang" , Pekka Enberg , Pekka Enberg , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , David Rientjes , Mel Gorman , "npiggin@kernel.dk" , "yanmin_zhang@linux.intel.com" , "Chen, Tim C" , "Li, Shaohua" In-Reply-To: References: <20101005185725.088808842@linux.com> <20101006123753.GA17674@localhost> <1286936472.31597.50.camel@debian> Content-Type: text/plain; charset="UTF-8" Date: Tue, 19 Oct 2010 08:01:44 +0800 Message-ID: <1287446504.24927.4.camel@debian> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2010-10-19 at 02:00 +0800, Christoph Lameter wrote: > On Wed, 13 Oct 2010, Alex,Shi wrote: > > > I got the code from > > git://git.kernel.org/pub/scm/linux/kernel/git/christoph/slab.git unified > > on branch "origin/unified" and do a patch base on 36-rc7 kernel. Then I > > tested the patch on our 2P/4P core2 machines and 2P NHM, 2P WSM > > machines. Most of benchmark have no clear improvement or regression. The > > testing benchmarks is listed here. > > http://kernel-perf.sourceforge.net/about_tests.php > > Ah. Thanks. The tests needs to show a clear benefit for this to be a > viable solution. They did earlier without all the NUMA queuing on SMP. > > > BTW, I save several time kernel panic in fio testing: > > =================== > > > Pid: 776, comm: kswapd0 Not tainted 2.6.36-rc7-unified #1 X8DTN/X8DTN > > > > RIP: 0010:[] [] slab_alloc > > > > +0x562/0x6f2 > > Cannot see the error message? I guess this is the result of a BUG_ON()? > I'll try to run that fio test first. > Can not see error messages since the machine hang when any ops appear. And the panic ops just pop up randomly, don't know how to reproduce it now.