diff options
author | Martin K. Petersen <martin.petersen@oracle.com> | 2012-09-18 16:19:32 (GMT) |
---|---|---|
committer | James Bottomley <JBottomley@Parallels.com> | 2012-11-14 06:45:42 (GMT) |
commit | 5db44863b6ebbb400c5e61d56ebe8f21ef48b1bd (patch) | |
tree | a352bab202b6cb40f234bd2fd306b54776543e8b /include/net | |
parent | 26e85fcd15f68b57d9ba645cd3591117a8ac0e05 (diff) | |
download | linux-5db44863b6ebbb400c5e61d56ebe8f21ef48b1bd.tar.xz |
[SCSI] sd: Implement support for WRITE SAME
Implement support for WRITE SAME(10) and WRITE SAME(16) in the SCSI disk
driver.
- We set the default maximum to 0xFFFF because there are several
devices out there that only support two-byte block counts even with
WRITE SAME(16). We only enable transfers bigger than 0xFFFF if the
device explicitly reports MAXIMUM WRITE SAME LENGTH in the BLOCK
LIMITS VPD.
- max_write_same_blocks can be overriden per-device basis in sysfs.
- The UNMAP discovery heuristics remain unchanged but the discard
limits are tweaked to match the "real" WRITE SAME commands.
- In the error handling logic we now distinguish between WRITE SAME
with and without UNMAP set.
The discovery process heuristics are:
- If the device reports a SCSI level of SPC-3 or greater we'll issue
READ SUPPORTED OPERATION CODES to find out whether WRITE SAME(16) is
supported. If that's the case we will use it.
- If the device supports the block limits VPD and reports a MAXIMUM
WRITE SAME LENGTH bigger than 0xFFFF we will use WRITE SAME(16).
- Otherwise we will use WRITE SAME(10) unless the target LBA is beyond
0xFFFFFFFF or the block count exceeds 0xFFFF.
- no_write_same is set for ATA, FireWire and USB.
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Reviewed-by: Mike Snitzer <snitzer@redhat.com>
Reviewed-by: Jeff Garzik <jgarzik@redhat.com>
Signed-off-by: James Bottomley <JBottomley@Parallels.com>
Diffstat (limited to 'include/net')
0 files changed, 0 insertions, 0 deletions