Messages in this thread |  | | | Date | Thu, 29 Jul 2010 21:50:54 +0300 | | Subject | Re: [2.6.35-rc6 patch] increase kmemleak robustness at boot | | From | Pekka Enberg <> |
| |
On Thu, Jul 29, 2010 at 9:03 PM, Daniel J Blueman <daniel.blueman@gmail.com> wrote: >> If it's just kmemleak_init() we're talking about, slab caches are up at that >> point so you can just use kmalloc(). > > The slab allocator isn't up at this point. With > CONFIG_DEBUG_KMEMLEAK_EARLY_LOG_SIZE set to 16K elements, an extra 3MB > of __initdata memory is used, but freed afterwards, and it works > great.
Right. I guess the required earlylog buffer size would be smaller if we initialized kmemleak earlier. Can we do that in mm_init() after kmem_cache_init()?
|  |