On 07/04/2012 06:19 PM, Mel Gorman wrote: > On Wed, Jul 04, 2012 at 03:26:17PM +0800, Lai Jiangshan wrote: >> MIGRATE_HOTREMOVE is a special kind of MIGRATE_MOVABLE, but it is stable: >> any page of the type can NOT be changed to the other type nor be moved to >> the other free list. >> >> So the pages of MIGRATE_HOTREMOVE are always movable, this ability is >> useful for hugepages and hotremove ...etc. >> >> MIGRATE_HOTREMOVE pages is the used as the first candidate when >> we allocate movable pages. >> >> 1) add small routine is_migrate_movable() for movable-like types >> 2) add small routine is_migrate_stable() for stable types >> 3) fix some comments >> 4) fix get_any_page(). The get_any_page() may change >> MIGRATE_CMA/HOTREMOVE types page to MOVABLE which may cause this page >> to be changed to UNMOVABLE. >> > > Reuse MIGRATE_CMA. Will do it. > Even if the pages are on the movable lists it should > not be a problem for memory hot-remove. It does have problem, unmovable pages may be allocated on it. The movable lists can be used for other type when ohter type is empty. Or we can rename current movable-lists to movable-preference-lists. Thanks, Lai -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
