On Fri, Oct 13, 2006 at 02:56:46PM +0400, Alex Tomas wrote: > >>>>> Theodore Tso (TT) writes: > > TT> I suggest this be tunable by superblock field, and not by a /proc > TT> tunable. This is the sort of thing which might be different > TT> per-filesystem, and the algorithm will be most effective if the > TT> filesystem always use the same cluster size from the time when it was > TT> first created. I'd be happy to assign a superblock field for this > TT> purpose, and add the appropriate tune2fs support if we have general > TT> agreement on this point. > > that would be good. there is even a stride option to mke2fs? Yes, there is. And just as we have -E stride=stripe-size and -E resize=max-online-resize, we can also -E cluster-size=bytes parameter in mke2fs. It would also make sense to make this be something that can be defaulted in /etc/mke2fs.conf, since even for IDE or SATA disks it probably makes sense to make the cluster size be 16k or 32k or maybe even higher. We probably need to do some benchmarks to see whether or not this makes sense. - Ted - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
