Date: Tue, 21 Mar 2006 08:55:20 +0530
From: Balbir Singh <balbir@in.ibm.com>
To: 7eggert@gmx.de
Cc: Pekka Enberg <penberg@cs.helsinki.fi>, akpm@osdl.org,
       linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slab: introduce kmem_cache_zalloc allocator
Message-ID: <20060321032520.GB8954@in.ibm.com>
Reply-To: balbir@in.ibm.com
References: <5Ssjj-314-69@gated-at.bofh.it> <5Sv7o-7l5-23@gated-at.bofh.it> <5Svh9-7xW-61@gated-at.bofh.it> <5SvK8-88q-41@gated-at.bofh.it> <E1FLPjT-0000o9-Sy@be1.lrz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E1FLPjT-0000o9-Sy@be1.lrz>
User-Agent: Mutt/1.5.10i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 669
Lines: 16

> > Ok, please keep the interface - build kmem_cache_zalloc() on top of
> > what I suggest.
> 
> The benefit of using *zalloc is the ability to skip the memset by using
> pre-zeroed memory or to use more efficient ways of zeroing a page.
> Having to check the value of a parameter wouldn't help.

Hmm... the current patch directly does a memset(). Are you talking about
possible optimizations to kmem_cache_zalloc()?

Balbir
-
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/