Re: [RFC] Extract kmalloc.h and slob.h from slab.h

[Nick Piggin <nickpiggin@yahoo.com.au>]

Christoph Lameter wrote:
> On Thu, 30 Nov 2006, Nick Piggin wrote:
> 
> 
>>OK, slab_defs.h and slob_defs.h would work, wouldn't it? That seems to be
>>the standard pattern used when alternatives become too numerous / complex
>>to be in a single file.
> 
> 
> Maybe better define a standard API and provide empty functions for slob?

There is a standard API, isn't there? It is the API used by the callers.
Ie. the one in slab.h, before slob came along.

So yes, we *have* to have all allocators using the same kmem_cache_t
framework. I don't see how a different API between slab and slob could
work?

> I think it would be feasable to have all slab allocators work within the 
> same kmem_cache_* framework. The kmalloc approaches are all different 
> though. So i would need kmalloc_slob and kmalloc_slab?

I see, I didn't realise kmalloc was different as well. I guess you could
follow the same approach. Probably don't bother splitting it, and just
move the kmalloc definitions to slab_defs.h / slob_defs.h?

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>