On Fri, Apr 24, 2009 at 04:37:17PM +0200, Carl Henrik Lunde wrote: > > On Fri, Apr 24, 2009 at 07:32, Martin K. Petersen <martin.petersen@xxxxxxxxxx> wrote: > > +What: ? ? ? ? ?/sys/block/<disk>/alignment > > +What: ? ? ? ? ?/sys/block/<disk>/<partition>/alignment > > +What: ? ? ? ? ?/sys/block/<disk>/queue/minimum_io_size > > +What: ? ? ? ? ?/sys/block/<disk>/queue/optimal_io_size > > Would it also be possible and useful to include the number of > spindles/channels, i.e., how many requests the device can handle > concurrently? CFQ could for example serve two time slices > concurrently if you have sequential reads and the device reports two > spindles. This is what we call "creeping featurism" (or other names not as nice). You'll then want to know which data are provided by which spindle. Then you'll want to know how fast each spindle is. Then you'll find that not all storage gives you that information (try asking an EMC Symmetrix how many spindles it has and where data is mapped ...) Let's just get something merged which gives us an improvement. Then you're free to experiment with adding the spindles count yourself, and if you can show a real advantage to it, come back and we can argue over it with data. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html