Re: [PATCH 09/14] target/configfs: Expose protection deviceattributes

From: Nicholas A. Bellinger
Date: Mon Jan 13 2014 - 13:29:17 EST


Hey MKP,

On Fri, 2014-01-10 at 16:01 -0500, Martin K. Petersen wrote:
> >>>>> "nab" == Nicholas A Bellinger <nab@xxxxxxxxxxxxx> 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.

> nab> pi_guard_type: Guard Type (1=DIF CRC, 2=IP CRC)
>
> 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.
>
> (scsi_debug supports IP checksum because it's both initiator and
> target).
>

In that case, dropping the IP checksum related code now..

--nab

--
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/