>>>>> "Sagi" == Sagi Grimberg <sa...@dev.mellanox.co.il> writes:
>> The IP checksum is only supported by DIX between OS and initiator, >> not by the target. I guess we could signal to the initiator via a >> vendor-private VPD that IP checksum is supported directly. But now >> what we have hardware-accelerated T10 CRC I don't think it's a big >> deal. Sagi> shouldn't it stick around if it is not deprecated yet, the Sagi> transport is required to support ip-csum->CRC conversion anyhow. SBC mandates that the guard tag on the wire and on the target device be the T10 CRC. The IP checksum is a DIX-optimization for application-HBA exchanges. The only place you should support the IP checksum is in the initiator. Note that you could conceivably do a T10 CRC to IP checksum conversion on writes received by the target and store the IP checksum on disk. And then convert back to T10 CRC when the data is eventually read. But it makes no sense to do that given that you will have to do the T10 CRC calculation regardless. Even if the backing store is DIX-capable and supports the IP checksum. -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
