On 09/23/2013 05:05 AM, Kirill A. Shutemov wrote: > To proof that the proposed changes are functional we enable the feature > for the most simple file system -- ramfs. ramfs is not that useful by > itself, but it's good pilot project. This does, at the least, give us a shared memory mechanism that can move between large and small pages. We don't have anything which can do that today. Tony Luck was just mentioning that if we have a small (say 1-bit) memory failure in a hugetlbfs page, then we end up tossing out the entire 2MB. The app gets a chance to recover the contents, but it has to do it for the entire 2MB. Ideally, we'd like to break the 2M down in to 4k pages, which lets us continue using the remaining 2M-4k, and leaves the app to rebuild 4k of its data instead of 2M. If you look at the diffstat, it's also pretty obvious that virtually none of this code is actually specific to ramfs. It'll all get used as the foundation for the "real" filesystems too. I'm very interested in how those end up looking, too, but I think Kirill is selling his patches a bit short calling this a toy. -- 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
