On Mon, 2014-01-13 at 10:52 -0800, James Bottomley wrote: > On Mon, 2014-01-13 at 10:30 -0800, Nicholas A. Bellinger wrote: > > Hey MKP, > > > > On Fri, 2014-01-10 at 16:01 -0500, Martin K. Petersen wrote: > > > >>>>> "nab" == Nicholas A Bellinger <n...@daterainc.com> writes: > > > > > > nab> This patch adds support for exposing DIF protection device > > > nab> attributes via configfs. This includes: > > > > > > nab> pi_prot_type: Protection Type (0, 1, 3 currently support) > > > nab> pi_prot_version: Protection Version (DIF v1 currently supported) > > > > > > What's DIF v2? > > > > > > > This would be the proposed 16-byte protection scheme for SBC4. > > What proposed 16 byte scheme? The only DIF proposals I know for SBC-4 > are 13-185R0 and 12-369R0 and that's a couple of new algorithms and > types because we cannot change the 8 byte PI. >
Then I'm probably getting the SBC version wrong.. It's the one that includes using CRC32C for the block guard, and larger space for reference tag as mentioned by MKP. --nab -- 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
