Re: [PATCH 07/14] target/sbc: Add P_TYPE + PROT_EN bits to READ_CAPACITY_16
From: Martin K. Petersen
Date: Sun Jan 12 2014 - 07:53:53 EST
>>>>> "Sagi" == Sagi Grimberg <sagig@xxxxxxxxxxxxxxxxxx> writes:
>> Per SBC, PI must be initialized to 0xffffffffffffffff. Since an app
>> tag value of 0xffff is an escape, this will prevent both target and
>> initiator from performing PI-verification when that block is read.
Sagi> OK, so this is an implicit escape (which will become explicit in
Sagi> DIX1.1?). So I will open that in DIF RDMA verbs.
DIX 1.0 says:
"If a storage device returns a value of 0xFFFF in the application tag
and the device is formatted with T10 PI Type 1 or 2 protection, the I/O
controller must disable integrity checking for that sector."
In DIX 1.1 it is explicit by way of the DIX_APP_ESCAPE flag.
--
Martin K. Petersen Oracle Linux Engineering
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/