+11
−13
Loading
Originally, the 'MAXIMUM WRITE SAME LENGTH' feild has dependence on Bdev UNMAP, once the Bdev has no support on UNMAP(Ex, AIO), the initiator side gets 0. According to spec: A MAXIMUM WRITE SAME LENGTH field set to a non-zero value indicates the maximum value that the device server accepts in the NUMBER OF LOGICAL BLOCKS field for a WRITE SAME command. A MAXIMUM WRITE SAME LENGTH field set to zero indicates that the device server does not report a limit on the number of logical blocks that may be requested for a single WRITE SAME command. Unlimited maximum blocks on a single request is not expected for SPDK, fix 'MAXIMUM WRITE SAME LENGTH' field. Change-Id: I2005156daa198afe0738236f32bfd61eeb3b8356 Signed-off-by:zhenwei pi <pizhenwei@bytedance.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/20401 Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by:
Shuhei Matsumoto <smatsumoto@nvidia.com> Community-CI: Mellanox Build Bot Reviewed-by:
Changpeng Liu <changpeng.liu@intel.com> Reviewed-by:
Jim Harris <jim.harris@samsung.com>