On 1/8/2014 10:36 PM, Nicholas A. Bellinger wrote:
From: Nicholas Bellinger n...@linux-iscsi.org
Hi MKP SCSI folks,
This series contains initial support for target mode DIF Type1+Type3
emulation within target core, RAMDISK_MCP device backend, and tcm_loop
fabric driver.
DIF emulation is
On Wed, 2014-01-15 at 20:03 +0200, sagi grimberg wrote:
On 1/8/2014 10:36 PM, Nicholas A. Bellinger wrote:
From: Nicholas Bellinger n...@linux-iscsi.org
Hi MKP SCSI folks,
This series contains initial support for target mode DIF Type1+Type3
emulation within target core, RAMDISK_MCP
nab == Nicholas A Bellinger n...@linux-iscsi.org writes:
nab The issue is that existing fs/bio-integrity.c code always assumes
nab client/initiator mode, in that it will attempt to
nab bio_integrity_generate() protection information in the submit_bio
nab WRITE path, and bio_integrity_verify() of
On Wed, 2014-01-15 at 20:42 -0500, Martin K. Petersen wrote:
nab == Nicholas A Bellinger n...@linux-iscsi.org writes:
nab The issue is that existing fs/bio-integrity.c code always assumes
nab client/initiator mode, in that it will attempt to
nab bio_integrity_generate() protection
nab == Nicholas A Bellinger n...@linux-iscsi.org writes:
nab Mmm, missed that detail. So that would take care of the
nab passthrough for the WRITE case then..
nab How about a passthrough on the READ completion side for target
nab fabrics doing a hardware VERIFY..? Any preferences how this
On 1/16/2014 3:42 AM, Martin K. Petersen wrote:
nab == Nicholas A Bellinger n...@linux-iscsi.org writes:
nab The issue is that existing fs/bio-integrity.c code always assumes
nab client/initiator mode, in that it will attempt to
nab bio_integrity_generate() protection information in the
Nic == Nicholas A Bellinger n...@daterainc.com writes:
Nic This series contains initial support for target mode DIF
Nic Type1+Type3 emulation within target core, RAMDISK_MCP device
Nic backend, and tcm_loop fabric driver.
Super cool! Do you have a git tree so I can start tinkering with this?
On Thu, 2014-01-09 at 21:00 -0500, Martin K. Petersen wrote:
Nic == Nicholas A Bellinger n...@daterainc.com writes:
Nic This series contains initial support for target mode DIF
Nic Type1+Type3 emulation within target core, RAMDISK_MCP device
Nic backend, and tcm_loop fabric driver.
Super
From: Nicholas Bellinger n...@linux-iscsi.org
Hi MKP SCSI folks,
This series contains initial support for target mode DIF Type1+Type3
emulation within target core, RAMDISK_MCP device backend, and tcm_loop
fabric driver.
DIF emulation is enabled via a new 'pi_prot_type' device attribute
within
9 matches
Mail list logo
