Martin K. Petersen wrote: > Jamie> Where it is due to specific values being not exactly right - > Jamie> like the subdevice offset (or modulo-offset) in MD because it > Jamie> doesn't represent all subdevices - it would be good for the > Jamie> info to have flags saying which _specific_ values are not > Jamie> exactly right. > > You get that traversing the sysfs tree. Ok. So I should always traverse the sysfs tree, and only use the leaf values, combining them at MD nodes as I see fit, and ignoring the values you provide at MD nodes? Is there enough information in sysfs for me to combine the values? I.e. offsets of all child disks, etc.? What about future compound disk types that my app doesn't know about? Use your values, I guess. > Jamie> So that programs can choose their heuristics appropriately. > Jamie> After all, users will use suboptimal layouts, and still want > Jamie> the best performance it can do. > > I'd like to keep a clear distinction between normal applications and > programs like mkfs. I'm targeting the latter. > > Given that filesystems can lay out files at will, I/O characteristics > for normal applications is really FIEMAP territory. I'm thinking of database type applications directly on block devices. They need similar performance guides as filesystems. You're right that most apps are FIEMAP territory. Vice versa: Filesystems on LVM may be FIEMAP territory, if there are many non-contiguous LVM strips, spanning multiple devices, LVM snapshots, etc. -- Jamie -- 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
