>>>>> "Dave" == Dave Chinner <david@xxxxxxxxxxxxx> writes: Dave> From what I've seen of the proposed SMR device standards, we're Dave> going to have to redesign filesystem allocation policies [...] The initial proposal involved SMR disks having a sparse LBA map carved into 2GB chunks. However, that was shot down pretty hard. The approach currently being worked uses either dynamic (flash, tiered storage) or static hints (SMR) to put things in an appropriate area given the nature of the I/O. This puts the burden of virtual to physical LBA management on the device rather than in the filesystem allocators. And gives us the benefit of having a single interface that can be used for many different device types. That said, the current proposal is crazy complex and clearly written with Windows in mind. They are creating different access profiles for .DLLs, .INI files, apps in the startup folder, and so on. Dave> Indeed, there is no end of different allocation policies a Dave> filesystem could define, so I don't think that iterating them in Dave> fadvise() is a good thing to do. I have no particular opinion on the proposed fadvise() flags. Just saying that no matter whether we like it or not we'll have to be able to pass information about expected access patterns down to the storage. -- Martin K. Petersen Oracle Linux Engineering -- 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
