The bdevio test app has some test cases verifying that write zeroes commands are handled correctly, but using knowledge of the ZERO_BUFFER_SIZE that the bdev library uses for splitting larger write zeroes commands. Instead of hardcoding that 1MB value in bdevio.c, have bdevio.c use ZERO_BUFFER_SIZE directly instead. But this requires moving ZERO_BUFFER_SIZE into bdev_internal.h and having bdevio.c include that file. We do this instead of putting ZERO_BUFFER_SIZE in the public API because we don't want users to make any kind of dependencies on this value. While here, also rename the tests that are using this value, so that the test names don't include any reference to the specific size of this bdev-internal zero buffer size. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: Ia29d92a706cb1f86b4c29374dc2a9beccf679208 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12383 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com> Reviewed-by: Shuhei Matsumoto <smatsumoto@nvidia.com> |
||
---|---|---|
.. | ||
bdev_internal.h | ||
bdev_rpc.c | ||
bdev_zone.c | ||
bdev.c | ||
Makefile | ||
part.c | ||
scsi_nvme.c | ||
spdk_bdev.map | ||
vtune.c |