James Bottomley wrote: > Um, your submission path is character. You pick up block again because > SCSI uses it for queues, but it's not really part of your paradigm. > I think your choice of using a character device will turn out to be a > design mistake because the migration path of existing filesystems is > bound to be a block device with extra features (which they may or may > not make use of) but only if there's a way to make ODS relevant to > users. We mount character devices already when it's appropriate. Look at JFFS, JFFS2, UBIFS and LOGFS. All of them operate on MTD devices, which are character device interfaces to flash storage, using the common MTD interface instead of the block layer. This is quite correct, because block devices have specific characteristics (generic block caching and ability to read/write each block independently) which neither flash nor OSDs have. Imho, OSDs are similar to flash in this respected. There is no fixed-size block/sector indexed storage device, therefore a block device would be wrong. Admittedly lumping everything else under "character" is daft, when you can't read and write character streams to the device, but that's unix for you. Character device used to mean serial ports etc. until it become "any old crap that's not a block device". :-) -- Jamie -- 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
