Not logged in
Log in now
Create an account
Subscribe to LWN
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
PostgreSQL 9.3 beta: Federated databases and more
LWN.net Weekly Edition for May 9, 2013
The idea is to tell your disk drive how you might expect to use the data later, and it will just sort everything out for you. Promise.
Maybe we should just encode the T10 spec in the VFS and allow filesystems to accept exactly the same hints and do the same things. Or maybe not.
I think if you really need that sort of control, you should make it all much more explicit. Create a /hot filesystem and a /cold filesystem and let that be that.
O_HOT and O_COLD
Posted Apr 26, 2012 19:35 UTC (Thu) by ejr (subscriber, #51652)
The question becomes what are the sufficient statistics necessary for control of what file goes where, and how (and how often) does the kernel update those statistics. While that *could* be handled at user level, intercepting open/close/read/write calls is kludgy and inefficient. IMHO, gathering the right statistics is where the kernel can help.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds