On 6/5/2014 12:20 AM, Nicholas A. Bellinger wrote:
Ping for the Mellanox folks..
Can someone please take a look at the WRITE_SAME logic on the ESX
initiator side that is triggering the bug that Moussa was/is hitting..?
Based upon the details below, it's clear that it's something specific to
the ESX initiator side, as we've been able to verify WRITE_SAME works as
expected with open-iscsi + iser, along with existing ESX iscsi + FC
initiators.
It would be nice to finally the last remaining VAAI primitive working
with the in-box ESX iser initiator. ;)
Hey Nic & Moussa,
So I gave write_same a shot with ESX iser initiator against LIO
(scsi_debug backing device),
and things seems to work (Nic, when I told you something wasn't working
I used RD backstore where this is not supported).
So do you have any other clues that can direct me where to look?
Cheers,
Sagi.
--
To unsubscribe from this list: send the line "unsubscribe target-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
