Recent Features
| |||||||||||||
Detecting kernel memory leaksDetecting kernel memory leaksPosted Jun 24, 2006 12:01 UTC (Sat) by nix (subscriber, #2304)In reply to: Detecting kernel memory leaks by liljencrantz Parent article: Detecting kernel memory leaks
The need for the registration function is mostly obviated by notifiers, AIUI. The halloc() function is rendered unnecessary by the slab allocator (that's what slabs are, blocks of memory containing many potential objects of the same type, initialized from a template and allocatable at lightning speed.)
(Log in to post comments)
Detecting kernel memory leaks Posted Jul 19, 2006 15:55 UTC (Wed) by liljencrantz (guest, #28458) [Link] Slabs are a performance hack to make some allocation patterns faster. This is completely different from halloc, which is a method for making memory deallocation significantly less cumbersome for the programmer. Both have the potential to waste less time and memory, but that is mainly a possible byproduct in the case of halloc.
Notifiers would work as a replacement for the halloc callback functions, but the result would be wordier and need more changes on existing code.
|
|||||||||||||