Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761341AbXJDScU (ORCPT ); Thu, 4 Oct 2007 14:32:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757665AbXJDScG (ORCPT ); Thu, 4 Oct 2007 14:32:06 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:43634 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756064AbXJDScE (ORCPT ); Thu, 4 Oct 2007 14:32:04 -0400 Subject: Re: SLUB performance regression vs SLAB From: Peter Zijlstra To: Arjan van de Ven Cc: Christoph Lameter , Matthew Wilcox , Nick Piggin , Christoph Hellwig , Mel Gorman , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, David Chinner , Jens Axboe In-Reply-To: <20071004105046.7b019fe8@laptopd505.fenrus.org> References: <20070919033605.785839297@sgi.com> <200709280742.38262.nickpiggin@yahoo.com.au> <200709281514.48293.nickpiggin@yahoo.com.au> <20071004161621.GO12049@parisc-linux.org> <20071004105046.7b019fe8@laptopd505.fenrus.org> Content-Type: text/plain Date: Thu, 04 Oct 2007 20:26:12 +0200 Message-Id: <1191522372.5574.39.camel@lappy> Mime-Version: 1.0 X-Mailer: Evolution 2.12.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1275 Lines: 32 On Thu, 2007-10-04 at 10:50 -0700, Arjan van de Ven wrote: > On Thu, 4 Oct 2007 10:38:15 -0700 (PDT) > Christoph Lameter wrote: > > > > Yeah the fastpath vs. slow path is not the issue as Siddha and I > > concluded earlier. Seems that we are mainly seeing cacheline bouncing > > due to two cpus accessing meta data in the same page struct. The > > patches in MM that are scheduled to be merged for .24 address > > > Ok every time something says anything not 100% positive about SLUB you > come back with "but it's fixed in the next patch set"... *every time*. > > To be honest, to me that sounds that SLUB isn't ready for prime time > yet, or at least not ready to be the only one in town... > > The day that the answer is "the kernel.org slub is fixing all the > issues" is when it's ready.. Arjan, to be honest, there has been some confusion on _what_ code has been tested with what results. And with Christoph not able to reproduce these results locally, it is very hard for him to fix it proper. - 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/