[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1389337238.5567.408.camel@haakon3.risingtidesystems.com>
Date: Thu, 09 Jan 2014 23:00:38 -0800
From: "Nicholas A. Bellinger" <nab@...ux-iscsi.org>
To: Sagi Grimberg <sagig@...lanox.com>
Cc: "Nicholas A. Bellinger" <nab@...erainc.com>,
target-devel <target-devel@...r.kernel.org>,
linux-scsi <linux-scsi@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Christoph Hellwig <hch@....de>, Hannes Reinecke <hare@...e.de>,
Or Gerlitz <ogerlitz@...lanox.com>
Subject: Re: [PATCH 09/14] target/configfs: Expose protection device
attributes
On Thu, 2014-01-09 at 13:01 +0200, Sagi Grimberg wrote:
> On 1/8/2014 10:36 PM, Nicholas A. Bellinger wrote:
> > From: Nicholas Bellinger <nab@...ux-iscsi.org>
> >
> > This patch adds support for exposing DIF protection device
> > attributes via configfs. This includes:
> >
> > pi_prot_type: Protection Type (0, 1, 3 currently support)
> > pi_prot_version: Protection Version (DIF v1 currently supported)
> > pi_guard_type: Guard Type (1=DIF CRC, 2=IP CRC)
> >
> > Within se_dev_set_pi_prot_type() it also adds the se_subsystem_api
> > device callbacks to setup per device protection information.
>
> Suggestion, expose pi_prot_format and call transport->init_prot() there.
> It is more explicit
> and this routine should be called upon getting FORMAT_UNIT as well.
<nod>, working on this next for FILEIO following your original example
code.
Thanks Sagi!
--nab
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists