On 05/22/2013 06:51 AM, Kirill A. Shutemov wrote: > Dave Hansen wrote: >> Also, what happens if "transparent_hugepage_flags & >> (1<<TRANSPARENT_HUGEPAGE_PAGECACHE)" becomes false at runtime and you >> have some already-instantiated huge page cache mappings around? Will >> things like mapping_align_mask() break? > > We will not touch existing huge pages in existing VMAs. The userspace can > use them until they will be unmapped or split. It's consistent with anon > THP pages. > > If anybody mmap() the file after disabling the feature, we will not > setup huge pages anymore: transparent_hugepage_enabled() check in > handle_mm_fault will fail and the page fill be split. > > mapping_align_mask() is part of mmap() call path, so there's only chance > that we will get VMA aligned more strictly then needed. Nothing to worry > about. Could we get a little blurb along those lines somewhere? Maybe even in your docs that you've added to Documentation/. Oh, wait, you don't have any documentation? :) You did add a sysfs knob, so you do owe us some docs for it. "If the THP-cache sysfs tunable is disabled, huge pages will no longer be mapped with new mmap()s, but they will remain in place in the page cache. You might still see some benefits from read/write operations, etc..." -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>