[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52D286FB.2070108@dev.mellanox.co.il>
Date: Sun, 12 Jan 2014 14:13:47 +0200
From: Sagi Grimberg <sagig@....mellanox.co.il>
To: "Martin K. Petersen" <martin.petersen@...cle.com>,
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>,
Christoph Hellwig <hch@....de>, Hannes Reinecke <hare@...e.de>,
Or Gerlitz <ogerlitz@...lanox.com>,
Nicholas Bellinger <nab@...ux-iscsi.org>
Subject: Re: [PATCH 07/14] target/sbc: Add P_TYPE + PROT_EN bits to READ_CAPACITY_16
On 1/10/2014 10:39 PM, Martin K. Petersen wrote:
>>>>>> "Sagi" == Sagi Grimberg <sagig@...lanox.com> writes:
> Sagi> What about FORMAT_UNIT emulation? The backstore protection
> Sagi> configuration is done at the target side via configfs/targetcli,
>
> I don't know of any non-disk devices that actually implement FORMAT
> UNIT. Usually such configuration is done using the array management
> interface.
>
Hmm,
So this takes me to a corner I still don't understand, if a LUN is
pre-formatted as T10-protected, what happens to unwritten blocks read?
I mean, SCSI login executes some reads from several LBAs which will
probably fail as blocks are unwritten.
What is the usage model? perform Initiator login and then format the LUN
on the target node? This is why I thought FORMAT_UNIT should be implemented.
I understand this corner will disappear in DIF v2 (following DIX1.1
draft) with ESCAPE flags.
--
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