Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 27 Apr 2002 15:53:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 27 Apr 2002 15:53:49 -0400 Received: from lightning.swansea.linux.org.uk ([194.168.151.1]:50962 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Sat, 27 Apr 2002 15:53:49 -0400 Subject: Re: [PATCH] (repost) kmem_cache_zalloc To: hch@infradead.org (Christoph Hellwig) Date: Sat, 27 Apr 2002 21:11:48 +0100 (BST) Cc: sandeen@sgi.com (Eric Sandeen), linux-kernel@vger.kernel.org, torvalds@transmeta.com, marcelo@conectiva.com.br In-Reply-To: <20020425094143.A17406@infradead.org> from "Christoph Hellwig" at Apr 25, 2002 09:41:43 AM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > caches, and a memset directly after the alloc destroys the object state. > A kmen_zalloc/kzalloc might make more sense. s/kzalloc/kcalloc/ Then our api continues to remind people of the C one so is easier to remember (and we need calloc stuff anyway in multiple places) - 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/