>>>>> "Hannes" == Hannes Reinecke <hare@xxxxxxx> writes: Hannes> Plus (as hch rightly pointed out) as there is no defined Hannes> userland interface the question is why we bother with all the Hannes> DIX stuff in the block layer. Because it catches problems in the path between block layer and HBA ASIC? FWIW, we find more issues there than we do between initiator and target. API issues aside, another reason adoption has been slow is that very few applications truly care about this stuff. The current approach in which data is protected when the I/O is submitted by the filesystem is good enough for most things. Saves the filesystem people the trouble of dealing with it too. In reality there are only a handful of applications that would actually benefit from an explicit userland API. Mostly in the database department. All the potential consumers of an interface I talked to wanted to use aio so that's why we've focused our efforts there. Both Darrick and I have been busy with other projects the last little while. I'll start looking at this again when I'm done with copy offload... -- Martin K. Petersen Oracle Linux Engineering -- 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
