On Mon, 16 Aug 2010, Naoya Horiguchi wrote: > In my understanding, in current code "other processors increasing refcount > during migration" can happen both in non-hugepage direct I/O and in hugepage > direct I/O in the similar way (i.e. get_user_pages_fast() from dio_refill_pages()). > So I think there is no specific problem to hugepage. > Or am I missing your point? With a single page there is the check of the refcount during migration after all the references have been removed (at that point the page is no longer mapped by any process and direct iO can no longer be initiated without a page fault. I see that you are running try_to_unmap() from unmap_and_move_huge_page(). I dont see a patch adding huge page support to try_to_unmap though. How does this work? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>