RE: kmem_cache_init() question

["Prashanth C." <cprash@wipinfo.soft.net>]

> On Tue, 15 Jun 1999 13:39:12 +0530, "Prashanth C."
> <cprash@wipinfo.soft.net> said:
>
>> I found that num_physpages is initialized in mem_init() function
>> (arch/i386/mm/init.c).  But start_kernel() calls kmem_cache_init() before
>> mem_init().  So, num_physpages will always(?) be zero when the above code
>> segment is executed.
>
>> Is num_physpages is initialized somewhere else before kmem_cache_init()
is
>> called by start_kernel()?
>
> The great thing about having all the source code is that if you can't
> instantly find the answer to such a question just by searching code, it
> takes no time at all to add a
>
>	printk ("num_physpages is now %lu\n", num_physpages);
>
> to init.c to find out for yourself. :)
>
> And if this turns out to be a real bug, do let us know...
>
> --Stephen

Yes, it is a bug.  Infact I found this bug when I tried to print values of
few varibles in kmem_cache_init() using printk().  Since, I have just now
started getting familiar with the MM code, I was not sure if I was missing
something :)

- Prashanth

--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/