> > Perhaps the filesystem driver or mkfs could > > probe for the stride in those cases? If the code asks for, say, 10MiB of > > data from the block device and it gets back sectors that are spaced > > 128KiB apart before it gets the rest of the data, it can make an > > intelligent guess about the stride. > > do you mean incorporation > storage benchmark in the mount procedure? Yes. If the benefits of automatically aligning on-disk data structures to the stride of the array are great enough, then a storage mini-benchmark may be of use. For example, suppose we have an array with a stride of 1MiB and the filesystem driver requests 10MiB of contiguous data from the start of the block device. Then the data at +0MiB from the start of the device, the data at +1MiB, the data at +2MiB, and so on ought to arrive earlier the data at, say, +0.5MiB, +1.5MiB and +2.5MiB. This would allow the filesystem driver to detect the stride even when the striping isn't being done by the MD or LVM/DM drivers in Linux (which, apparently, have well-defined interfaces for discovering the stride in software). I imagine this would work well for a run-of-the-mill hardware RAID card in a PC. However, as you pointed out in your original email, there are SANs to be considered. If another host is putting load on the SAN, it could throw off the read timings and cause the filesystem driver to make a bad guess. Cheers, Eric
Attachment:
signature.asc
Description: This is a digitally signed message part
