Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753110AbaAMTZk (ORCPT ); Mon, 13 Jan 2014 14:25:40 -0500 Received: from mail.linux-iscsi.org ([67.23.28.174]:33431 "EHLO linux-iscsi.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752531AbaAMTZc (ORCPT ); Mon, 13 Jan 2014 14:25:32 -0500 Message-ID: <1389641243.5567.445.camel@haakon3.risingtidesystems.com> Subject: Re: [PATCH 09/14] target/configfs: Expose protection device attributes From: "Nicholas A. Bellinger" To: James Bottomley Cc: "Martin K. Petersen" , "Nicholas A. Bellinger" , target-devel , linux-scsi , linux-kernel , Christoph Hellwig , Hannes Reinecke , Sagi Grimberg , Or Gerlitz Date: Mon, 13 Jan 2014 11:27:23 -0800 In-Reply-To: <1389639177.12062.21.camel@dabdike.int.hansenpartnership.com> References: <1389212157-14540-1-git-send-email-nab@daterainc.com> <1389212157-14540-10-git-send-email-nab@daterainc.com> <1389637859.5567.431.camel@haakon3.risingtidesystems.com> <1389639177.12062.21.camel@dabdike.int.hansenpartnership.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 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-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/