>>>>> "Sagi" == Sagi Grimberg <sagig@xxxxxxxxxxxxxxxxxx> writes: Sagi, Sagi> I thought that WRITE_SAME with DIX would include PI for the block Sagi> that is being sent over the wire, the initiator and target HBAs Sagi> will verify the single block integrity and the target backend will Sagi> expand the PI for the number of same sectors involved (unless the Sagi> target backend includes another wire, in this case it should Sagi> handle it like the initiator...) Yep. I'm just saying there's nothing to be done wrt. DIX and WRITE SAME on the initiator side. If you were to do something special it would effectively mean turning WRITE SAME into a WRITE which kind of defeats the purpose. >> In target mode it is conceivable to set up a prot sgl after parsing >> the CDB and let the HBA do the work. But I'm not aware of any >> hardware that allows that. Sagi> I don't either, I think it would be simpler to have the target Sagi> core implement it instead of having each fabric driver doing the Sagi> same thing. Yep. Sagi> The initiator can pass PI for the block that is transferred, and Sagi> the target is responsible to handle it. The target will also pass Sagi> this single block with PI to it's backend. The backend is Sagi> responsible to update PI for all the sectors that are written. Sagi> Sounds right? Yes, I agree. -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
