On Wed, 9 May 2007, Nick Piggin wrote: > Right. You only need to know blob boundaries for free blobs (so you can > allocate from or merge to). For allocated blobs, you know the start > (which is the address of the memory), and the end (which is the start + > the size contained in kmem_cache structure). For kmalloc caches you will not have the object size on kfree. In that case the slob_t structure is needed before the object. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: + fix-spellings-of-slab-allocator-section-in-init-kconfig.patch added to -mm tree
- From: Christoph Lameter <[email protected]>
- Re: + fix-spellings-of-slab-allocator-section-in-init-kconfig.patch added to -mm tree
- From: David Miller <[email protected]>
- Re: + fix-spellings-of-slab-allocator-section-in-init-kconfig.patch added to -mm tree
- From: Christoph Lameter <[email protected]>
- Re: + fix-spellings-of-slab-allocator-section-in-init-kconfig.patch added to -mm tree
- From: David Miller <[email protected]>
- Re: + fix-spellings-of-slab-allocator-section-in-init-kconfig.patch added to -mm tree
- From: Nick Piggin <[email protected]>
- Re: + fix-spellings-of-slab-allocator-section-in-init-kconfig.patch added to -mm tree
- Prev by Date: Re: + fix-spellings-of-slab-allocator-section-in-init-kconfig.patch added to -mm tree
- Next by Date: Re: [patches] [PATCH] [21/22] x86_64: Extend bzImage protocol for relocatable bzImage
- Previous by thread: Re: + fix-spellings-of-slab-allocator-section-in-init-kconfig.patch added to -mm tree
- Next by thread: Re: + fix-spellings-of-slab-allocator-section-in-init-kconfig.patch added to -mm tree
- Index(es):
 |