[lkml]   [2001]   [Jun]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Simple example of using slab allocator?
Matthew Dharm writes:
> For 2.5, I'm planning on switching my driver over to the slab allocator,
> for a variety of reasons. Does anyone have a _dead_ simple example of how
> to use such a beast? I've seen the various web pages and document
> explaining the API, but I love to see working examples for reference (and
> to fill in the blanks).

The slab allocator IS dead simple to use, basically:

- driver global variable:

kmem_cache_t *usb_mass_cachep;

- in the driver init function:

usb_mass_cachep = kmem_cache_create("usb_mass_cache",
sizeof(struct whatever),
(check for NULL usb_mass_slab)

- in the driver cleanup function:

if (usb_mass_cachep && kmem_cache_destroy(usb_mass_cachep))
printk(KERN_ERR "usb_mass_cache: not all structures freed\n");

- wherever you need an item from the slab cache:

whateverp = kmem_cache_alloc(usb_mass_cachep, GFP_KERNEL);
(check for NULL whateverp)

- when you are done with it:

kmem_cache_free(usb_mass_cachep, whateverp);

- if you have a slab leak and you don't free all of the items (hence the slab
cache is not removed), you will probably get an oops when you reload the
driver. You can only have one slab cache per name ("usb_mass_cache" here).
- You may need different alignment (SLAB_HWCACHE_ALIGN), or not
- You may need different allocation policy (GFP_KERNEL), or not

Cheers, Andreas
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?" -- Dogbert
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:17    [W:0.036 / U:8.844 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site