Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423204AbWCUSh2 (ORCPT ); Tue, 21 Mar 2006 13:37:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1423130AbWCUSh1 (ORCPT ); Tue, 21 Mar 2006 13:37:27 -0500 Received: from courier.cs.helsinki.fi ([128.214.9.1]:57988 "EHLO mail.cs.helsinki.fi") by vger.kernel.org with ESMTP id S1423204AbWCUShX (ORCPT ); Tue, 21 Mar 2006 13:37:23 -0500 Subject: Re: [PATCH] slab: introduce kmem_cache_zalloc allocator From: Pekka Enberg To: Manfred Spraul Cc: Andrew Morton , linux-kernel@vger.kernel.org In-Reply-To: <44204754.8070401@colorfullife.com> References: <20060321023654.389dc572.akpm@osdl.org> <44204754.8070401@colorfullife.com> Date: Tue, 21 Mar 2006 20:37:21 +0200 Message-Id: <1142966242.23941.0.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Evolution 2.4.2.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 609 Lines: 14 On Tue, 2006-03-21 at 19:35 +0100, Manfred Spraul wrote: > One minor point: There are two cache_alloc entry points: __cache_alloc, > which is a forced inline function, and kmem_cache_alloc, which is just a > wrapper for __cache_alloc. Is it really necessary to call __cache_alloc? Unfortunately, yes. Using kmem_cache_alloc screws up caller tracing. Pekka - 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/