iSCSI needs to be at least aware that a task involves protection
information. In case it does, after the transaction completed
libiscsi will ask the transport to check the protection status
of the transaction.
Unlike transport errors, DIF errors should not prevent successful
completion of the tran
On Wed, Mar 5, 2014 at 7:43 PM, Sagi Grimberg wrote:
>
> iSCSI needs to be at least aware that a task involves protection
> information. In case it does, after the transaction completed
> libiscsi will ask the transport to check the protection status
> of the transaction.
>
> Unlike transport erro
On 03/17/2014 02:25 AM, Or Gerlitz wrote:
> On Wed, Mar 5, 2014 at 7:43 PM, Sagi Grimberg wrote:
>> >
>> > iSCSI needs to be at least aware that a task involves protection
>> > information. In case it does, after the transaction completed
>> > libiscsi will ask the transport to check the protectio
On 3/17/2014 6:59 PM, Mike Christie wrote:
This patch is ok, but happened to the patch for the xmit task path?
Hey Mike, Thanks for your Ack on this.
The xmit_task fix was posted as a separate patch since it is
not specific to this set (relevant also for existing data dma_mapping in
xmit_t
On Mon, Mar 17, 2014, Sagi Grimberg wrote:
> On 3/17/2014 6:59 PM, Mike Christie wrote:
>> This patch is ok, but happened to the patch for the xmit task path?
> Hey Mike, Thanks for your Ack on this.
> The xmit_task fix was posted as a separate patch since it is not specific
> to this set (relev
5 matches
Mail list logo