Thanks, much clearer now. But my next question would be how to
distinguish such order > 0 pages from memory-leaked pages. I'd like to
modify the show_mem function so that its "free pages" count exactly
agrees with the freelist, in the absence of leaks.
When an order > 0 page is released, does the memory allocator sweep up
all trailing adjacent pages with count = 0 and assume they were part of
the initial allocation?
Regards,
Bill