![]() | |||||||||||||
Messages in this thread |
On Thu, 26 Jan 2006, Matthew Dobson wrote: > I decided that using a whole page allocator would be the easiest way to > cover the most common uses of slab/kmalloc, but your idea is very > interesting. My immediate concern would be trying to determine, at kfree() > time, what was allocated by the slab allocator and what was allocated by > the critical pool. I will give this approach more thought, as the idea of > completely separating the critical pool and slab allocator is attractive. I think you can use PageSlab for that. Pekka - 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/ | ||||||||||||
| Last update: 2006-01-27 07:13 [from the cache] ©2003-2008 | |||||||||||||