> Can you clarify what you mean above with an example? I don't really
> follow.
Sure, take 'tar' as an example. It'll read files in the order that
their names are returned from directory listing. This can produce bad
IO patterns because the order in which the file names are returned
doesn't match the order of the file's blocks on disk. (htree, I'm
looking at you!)
People have noticed that tar-like loads can be sped up greatly just by
sorting the files by their inode number as returned by stat(), never
mind the file blocks themselves. One example of this is Chris Mason's
'acp'.
http://oss.oracle.com/~mason/acp/
The logical extension of that is to use FIBMAP to find the order of file
blocks on disk and then doing IO on blocks in sorted order. It'd take
work to write an app that does this reliably, sure.
In this use the application doesn't actually care what the absolute
numbers are. It cares about their ordering. File systems would be able
to chose whatever scheme they wanted for the actual values of the
results from a FIBMAP-alike as long as the sorting resulted in the right
IO patterns.
Arguing that this use is significant enough to justify an addition to
the file system API is a stretch. I'm just sharing the observation.
- z
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
