Andrew Morton wrote: > On Tue, 24 Sep 2013 16:49:50 -0700 Andi Kleen <ak@xxxxxxxxxxxxxxx> wrote: > > > > At the very least we should get this done for a real filesystem to see > > > how intrusive the changes are and to evaluate the performance changes. > > > > That would give even larger patches, and people already complain > > the patchkit is too large. > > The thing is that merging an implementation for ramfs commits us to > doing it for the major real filesystems. Before making that commitment > we should at least have a pretty good understanding of what those > changes will look like. > > Plus I don't see how we can realistically performance-test it without > having real physical backing store in the picture? My plan for real filesystem is to get it first beneficial for read-mostly files: - allocate huge pages on read (or collapse small pages) only if nobody has the inode opened on write; - split huge page on write to avoid dealing with write back patch at first and dirty only 4k pages; This will will get most of elf executables and libraries mapped with huge pages (it may require dynamic linker change to align length to huge page boundary) which is not bad for start. -- Kirill A. Shutemov -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
