Hi Andrew, The following patches address points brought up during review of the grouping pages by mobility patches. The main aim of this patchset is to group pages by an order other than MAX_ORDER-1 and provide some statistics but there is also one bug fix at the start of the patchset.
Changelog since v2 o Patches acked by Christoph Changelog since v1 of statistics and grouping by arbitrary order o Fix a bug in move_freepages_block() calculations o Make page_order available in internal.h for PageBuddy pages o Rename fragavoidance to pagetypeinfo for both code and proc filename o Renamr nr_pages_pageblock to pageblock_nr_pages for consistency o Print out pageblock_nr_pages and pageblock_order in proc output o Print out the orders in the header for /proc/pagetypeinfo o The order being grouped at is no longer printed to the kernel log. The necessary information is available in /proc/pagetypeinfo o Breakout page_order so that statistics do not require special knowledge of the buddy allocator The first patch is a fix to move_freepages_block() where it calculates the number of blocks used instead of the number of base pages which is what we are really interested in. This is a bug fix. The second patch moves page_order() to internal.h as it is needed by the statistics patch later in the patchset. It is also needed by the not-ready-for-posting-yet memory compaction prototype. The third patch allows grouping by mobility at sizes other than MAX_ORDER_NR_PAGES. The size is based on the order of the system hugepage where that is defined. When possible this is specified as a compile time constant to help the optimiser. It does change the handling of hugepagesz from __setup() to early_param() which needs looking at. The fourth and fifth patches provide some statistics in relation to fragmentation avoidance. The statistics patches are split as the second set depend on information from PAGE_OWNER when it's available. -- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
