The NVMHCI working group has specified [1] a set of attributes for filesystems to pass down to devices which may allow the device to lay out its storage more effectively (eg if it's a hybrid MLC/SLC device). For Enterprise NVMHCI, the working group is looking at refining these hints. Are there any hints that people would like to see added or removed from the list in NVMHCI 1.0? I think there are some hints that are hard for the filesystem to know itself, never mind pass down, so it'd be good to remove them to reduce the complexity. Contrariwise, there are some hints I think the filesystem could pass down that aren't in the spec today, such as the flags from madvise (random access vs sequential access) and whether the access is for fs metadata or application data. [1] http://www.intel.com/standards/nvmhci/index.htm Page 35, figure 26 -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- 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
