From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753742AbZFOL2e (ORCPT ); Mon, 15 Jun 2009 07:28:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751898AbZFOL20 (ORCPT ); Mon, 15 Jun 2009 07:28:26 -0400 Received: from cantor.suse.de ([195.135.220.2]:59440 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751555AbZFOL20 (ORCPT ); Mon, 15 Jun 2009 07:28:26 -0400 Date: Mon, 15 Jun 2009 13:28:28 +0200 From: Nick Piggin To: Benjamin Herrenschmidt Cc: Pekka Enberg , Heiko Carstens , torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, cl@linux-foundation.org, kamezawa.hiroyu@jp.fujitsu.com, lizf@cn.fujitsu.com, mingo@elte.hu, yinghai@kernel.org Subject: Re: [GIT PULL v2] Early SLAB fixes for 2.6.31 Message-ID: <20090615112827.GC6012@wotan.suse.de> References: <20090615081831.GA5411@osiris.boeblingen.de.ibm.com> <84144f020906150210w7fa29042xc12efb4a087e3d26@mail.gmail.com> <20090615094148.GC1314@wotan.suse.de> <1245059476.12400.7.camel@pasglop> <20090615101254.GB10294@wotan.suse.de> <1245062388.12400.17.camel@pasglop> <20090615112205.GA6012@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090615112205.GA6012@wotan.suse.de> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 15, 2009 at 01:22:05PM +0200, Nick Piggin wrote: > On Mon, Jun 15, 2009 at 08:39:48PM +1000, Benjamin Herrenschmidt wrote: > But I won't live with having it shit in our nice core code... > Well, at least I won't throw up my hands and give up this > early. Just the principle, btw. The cost of this one load and branch (when moved out to the slowpath -- in the fastpath then adding a single cycle is like a 1% slowdown you know) is not prohibitive, but it's a slipperly slope. If a couple of specialised early boot code places have to test slab_is_available() to prevent crap leaking into our main allocators, then that's quite fine by me.