| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20100722180854.GB22009@parisc-linux.org> Date: Thu, 22 Jul 2010 12:08:54 -0600 From: Matthew Wilcox <matthew@....cx> To: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Filesystem hints to storage 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-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists