From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 25 Jul 2007 11:56:27 -0700 (PDT) From: Christoph Lameter Subject: Re: Slab API: Remove useless ctor parameter and reorder parameters In-Reply-To: <84144f020707250333gc1c2f01l24c7b9ff6211a489@mail.gmail.com> Message-ID: References: <20070724165914.a5945763.akpm@linux-foundation.org> <20070724175332.41ade708.akpm@linux-foundation.org> <84144f020707250333gc1c2f01l24c7b9ff6211a489@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Pekka Enberg Cc: Andrew Morton , linux-mm@kvack.org List-ID: On Wed, 25 Jul 2007, Pekka Enberg wrote: > We're gonna have API breakage with kmem_cache_ops thing too, right? Not in the initial envisioned form. The unused pointer argument would have simply change type leaving kmem_cache_create as is. Now we may have to add a function to set the kmem_cache_ops to avoid API changes. Or we change the ctor type argument to be kmem_cache_ops * (as you wanted earlier). However that would require allocating a kmem_cache_ops structure for each slab that uses an initializer. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org