On Wed, 2014-05-28 at 23:52 -0400, Martin K. Petersen wrote: > Implement support for hardware copy offload. This initial implementation > only supports EXTENDED COPY(LID1). If need be we can add support for > LID4 or token copy at a later date. > > If a device has the 3PC flag set in the standard INQUIRY response we'll > issue a RECEIVE COPY OPERATION PARAMETERS command. We require the device > to support two copy source/copy destination descriptors and one block to > block (0x02) segment descriptor. The device must support the NAA > identification descriptor (0xE4). If the device is capable we'll set the > queue limits to indicate that the device supports copy offload. > > The copy block range limit can be overridden in scsi_disk's > max_copy_block sysfs attribute. > > sd_setup_copy_command() is used to prepare any REQ_COPY requests. The > relevant descriptors are placed in a payload page akin to REQ_DISCARD. > > Signed-off-by: Martin K. Petersen <martin.peter...@oracle.com> > --- > drivers/scsi/sd.c | 254 > ++++++++++++++++++++++++++++++++++++++++++++- > drivers/scsi/sd.h | 4 + > include/scsi/scsi_device.h | 1 + > 3 files changed, 257 insertions(+), 2 deletions(-) >
Looks good. Nice work. ;) Reviewed-by: Nicholas Bellinger <n...@linux-iscsi.org> -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
