Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 3 Apr 2002 17:29:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 3 Apr 2002 17:29:40 -0500 Received: from [12.150.248.132] ([12.150.248.132]:52786 "EHLO dhcp-177.hsv.redhat.com") by vger.kernel.org with ESMTP id ; Wed, 3 Apr 2002 17:29:26 -0500 Date: Wed, 3 Apr 2002 16:28:10 -0600 From: Tommy Reynolds To: "Eric Sandeen" Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com, marcelo@conectiva.com.br Subject: Re: [PATCH] kmem_cache_zalloc() Message-Id: <20020403162810.2c24ba60.reynolds@redhat.com> In-Reply-To: <1017871982.25556.7.camel@stout.americas.sgi.com> Organization: Red Hat Software, Inc. / Embedded Development X-Mailer: Sylpheed version 0.7.4cvs29 (GTK+ 1.2.10; i686-pc-linux-gnu) X-Face: Nr)Jjr, spoke thus: > In short, we're using a kmem_cache_zalloc() function in XFS which just > does kmem_cache_alloc + memset. > > We'd like to incorporate this into the kernel proper, and several others > chimed in that it would be useful, so here's the patch. If it's a no-go > with you, we can roll this functionality back under fs/xfs to reduce our > changes in the mainline kernel. Why not use the constructor function interface to kmem_cache_create that is _already_ in the kernel API? - 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/