On Fri, Jul 9, 2010 at 8:01 PM, Mulyadi Santosa
wrote:
> On Sat, Jul 10, 2010 at 06:53, GoatZilla wrote:
>> When it hits slab_order:
>>
>> http://lxr.linux.no/linux+v2.6.34.1/mm/slub.c#L1958
>>
>> It finds that the minimum page order can hold more than
>>
Let's say I set my PAGE_SIZE to be a massive 1MB. This is a huge page
size, so it seems to make sense to have the min order for SLUB be 0.
While booting, the kernel sets up the kmalloc caches for, say, the 8
byte size type.
When it hits slab_order:
http://lxr.linux.no/linux+v2.6.34.1/mm/slub.c#
cond expected decrement, but I can't seem to find where the
first decrement is supposed to occur... Anybody happen to know?
Thanks again!
On Wed, Jun 17, 2009 at 12:02 PM, Mulyadi Santosa wrote:
> On 6/17/09, GoatZilla wrote:
> > Can someone explain what the normal path for
Can someone explain what the normal path for freeing a task's task_struct
resources after it's finished? I'm working on a 2.6.26.6 kernel which
doesn't seem to free these resources after a task is finished.
Apparently, release_task() is called which at least sets up most of the
work. The actual
I'm having trouble figuring out what this define is really supposed to refer
to. From the comments in the arch files, it seems to indicate a file offset
for pages that aren't present. What I don't understand is the number of
bits it's usually set to -- 28 or 29. This seems to be too many bits to
