On Oct 09, 2008 12:49 -0400, Theodore Ts'o wrote: > So I considered it a moral imperative to rewrite section 1.10 of > Documentation/filesystems/proc.txt. I *think* I got the definitions of > the mballoc tuning parameters correct, but the original text made it > hard to understand what exactly some of these tuning parameters meant, > and so I was forced to go RTFS. Alex, Andreas, could you quickly > double check the new documentation and make sure I got things right? Yes, looks reasonable. A detailed description of mb_history is in the Lustre user manual section 20.7 (URL below) and your description matches the remaining manual entries pretty well: http://manual.lustre.org/manual/LustreManual16_HTML/LustreProc.html#50642991_pgfId-1290686 Parameter Description pid Process that made the allocation. inode inode number allocated blocks goal Initial request that came to mballoc (group/block-in-group/number-of-blocks) result What mballoc actually found for this request. found Number of free chunks mballoc found and measured before the final decision. grps Number of groups mballoc scanned to satisfy the request. cr Stage at which mballoc found the result: 0 - best in terms of resource allocation. The request was 1MB or larger and was satisfied directly via the kernel buddy allocator. 1 - regular stage (good at resource consumption) 2 - fs is quite fragmented (not bad at resource consumption) 3 - fs is very fragmented (worst at resource consumption) queue Total bytes in active/queued sends. merge Whether the request hit the goal. This is good as extents code can now merge new blocks to existing extent, eliminating the need for extents tree growth. tail Number of blocks left free after the allocation breaks large free chunks. broken How large the broken chunk was. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
