>>>>> "hch" == hch@infradead org <hch@xxxxxxxxxxxxx> writes: hch> read_capacity_16 calls sd_config_discard(sdkp, SD_LBP_WS16) if the hch> LPBME bit is set. At least older SBC drafts left it wide open if a hch> target supports WRITE SAME with UNMAP or UNMAP in this case. Correct. hch> So I think we'd still want a patch to use UNMAP instead of WRITE hch> SAME for this case, which should also fix hyperv. There are lots of devices out there that support WRITE SAME(10) or (16) without the UNMAP bit. And there are devices that support WRITE SAME w/ UNMAP functionality but not "regular" WRITE SAME. no_write_same is there to prevent the REQ_WRITE_SAME use case (for which we have really weak heuristics). Your patch overloads no_write_same so it also governs a REQ_DISCARD use case. My proposed black list patch fixes the hyperv discard issue. So I don't see why we'd need to overload no_write_same which was meant for an entirely different purpose. -- Martin K. Petersen Oracle Linux Engineering -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
