>> Note also that something (not sure what) has made fragmentation
>> increasingly prevalent over the years since the buddy allocator
>> was originally put in.
>
> Actually it seems to be situations like the stack now being two pages
Instrumentation posted here before appears to corellate fragmentation
being /caused/ with I/O activity (single bonnie process and thus a
single 8k stack frame). My own guess is that it is due to
a different persistence of various caches.
I haven't seen anyone before blaming stack frame allocation
as a /cause/ of fragmenation - I've heard people say they
notice fragmentation more as stack frame allocs start to
fail - but that's a symptom.
-- Alex Bligh - 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/