On 11/4/2013 8:41 PM, Nicholas A. Bellinger wrote:
On Sat, 2013-11-02 at 14:57 -0700, Bart Van Assche wrote:
On 1/11/2013 18:36, Nicholas A. Bellinger wrote:
On Fri, 2013-11-01 at 08:03 -0700, Bart Van Assche wrote:
On 31/10/2013 5:24, Sagi Grimberg wrote:
In T10-DIF, when a series of
On Tue, 2013-11-05 at 11:13 +0200, Sagi Grimberg wrote:
On 11/4/2013 8:41 PM, Nicholas A. Bellinger wrote:
On Sat, 2013-11-02 at 14:57 -0700, Bart Van Assche wrote:
On 1/11/2013 18:36, Nicholas A. Bellinger wrote:
On Fri, 2013-11-01 at 08:03 -0700, Bart Van Assche wrote:
On 31/10/2013
On Sat, 2013-11-02 at 14:57 -0700, Bart Van Assche wrote:
On 1/11/2013 18:36, Nicholas A. Bellinger wrote:
On Fri, 2013-11-01 at 08:03 -0700, Bart Van Assche wrote:
On 31/10/2013 5:24, Sagi Grimberg wrote:
In T10-DIF, when a series of 512-byte data blocks are transferred, each
block is
On 11/2/2013 12:06 AM, Bart Van Assche wrote:
On 31/10/2013 5:24, Sagi Grimberg wrote:
While T10-DIF clearly defines that over the wire protection guards are
interleaved into the data stream (each 512-Byte block followed by 8-byte
guard), when in memory, the protection guards may reside in a
On 11/2/2013 12:06 AM, Bart Van Assche wrote:
On 31/10/2013 5:24, Sagi Grimberg wrote:
While T10-DIF clearly defines that over the wire protection guards are
interleaved into the data stream (each 512-Byte block followed by 8-byte
guard), when in memory, the protection guards may reside in a
On 31/10/2013 5:24, Sagi Grimberg wrote:
In T10-DIF, when a series of 512-byte data blocks are transferred, each
block is followed by an 8-byte guard. The guard consists of CRC that
protects the integrity of the data in the block, and some other tags
that protects against mis-directed IOs.
On Fri, 2013-11-01 at 08:03 -0700, Bart Van Assche wrote:
On 31/10/2013 5:24, Sagi Grimberg wrote:
In T10-DIF, when a series of 512-byte data blocks are transferred, each
block is followed by an 8-byte guard. The guard consists of CRC that
protects the integrity of the data in the block,
This patchset Introduces Verbs level support for signature handover
feature. Siganture is intended to implement end-to-end data integrity
on a transactional basis in a completely offloaded manner.
There are several end-to-end data integrity methods used today in various
applications and/or upper
Hi Sagi,
I wander what's the performance overhead with this DIF support?
And is there a roadmap for support SRP/ISER and target side for DIF?
Regards,
Jack
On 10/31/2013 01:24 PM, Sagi Grimberg wrote:
This patchset Introduces Verbs level support for signature handover
feature. Siganture is
On 10/31/2013 2:55 PM, Jack Wang wrote:
Hi Sagi,
I wander what's the performance overhead with this DIF support?
And is there a roadmap for support SRP/ISER and target side for DIF?
Regards,
Jack
Well, all DIF operations are fully offloaded by the HCA so we don't expect
any performance
On 10/31/2013 02:20 PM, Sagi Grimberg wrote:
On 10/31/2013 2:55 PM, Jack Wang wrote:
Hi Sagi,
I wander what's the performance overhead with this DIF support?
And is there a roadmap for support SRP/ISER and target side for DIF?
Regards,
Jack
Well, all DIF operations are fully offloaded
11 matches
Mail list logo
