On Wed, Sep 22, 2010 at 04:05:47PM -0500, Christoph Lameter wrote: > On Wed, 8 Sep 2010, Naoya Horiguchi wrote: > > > We can't use existing hugepage allocation functions to allocate hugepage > > for page migration, because page migration can happen asynchronously with > > the running processes and page migration users should call the allocation > > function with physical addresses (not virtual addresses) as arguments. > > Ummm... Some arches like IA64 need huge pages fixed at certain virtual > addresses in which only huge pages exist. A vma is needed in order to be > able to assign proper virtual address to the page. > Are you sure about this case? The virtual address of the page being migrated should not changed, only the physical address. > How does that work with transparent huge pages anyways? > IA-64 doesn't support transparent huge pages. Even if it did, this change is about hugetlbfs, not transparent huge page support. > This looks like its going to break IA64 hugepage support for good. How? > Maybe > thats okay given the reduced significance of IA64? Certainly would > simplify the code. > Currently I'm not seeing how IA-64 gets broken. -- Mel Gorman Part-time Phd Student Linux Technology Center University of Limerick IBM Dublin Software Lab -- 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>