Artur Paszkiewicz fed1f52b9e nvmef: don't set optimal I/O boundary if write_unit_size != 1 ... Optimal I/O boundary causes I/O to be split in the nvme driver. This is a problem for writes if write_unit_size > 1 because the split I/O may not match the write_unit_size. Fixes: #2791 Change-Id: I437e6cb6d8e2415658d5b46539feeacb5363fd46 Signed-off-by: Artur Paszkiewicz <artur.paszkiewicz@intel.com> Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/15627 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>		2022-11-30 08:50:29 +00:00
..
ctrlr_bdev.c	nvmef: don't set optimal I/O boundary if write_unit_size != 1	2022-11-30 08:50:29 +00:00
ctrlr_discovery.c	update Intel copyright notices	2022-11-10 08:28:53 +00:00
ctrlr.c	nvmf: Add copy command support	2022-11-30 08:50:06 +00:00
fc_ls.c	update Intel copyright notices	2022-11-10 08:28:53 +00:00
fc.c	update Intel copyright notices	2022-11-10 08:28:53 +00:00
nvmf.c	update Intel copyright notices	2022-11-10 08:28:53 +00:00
rdma.c	update Intel copyright notices	2022-11-10 08:28:53 +00:00
subsystem.c	update Intel copyright notices	2022-11-10 08:28:53 +00:00
tcp.c	nvmf: Add copy command support	2022-11-30 08:50:06 +00:00
transport.c	update Intel copyright notices	2022-11-10 08:28:53 +00:00
vfio_user.c	update Intel copyright notices	2022-11-10 08:28:53 +00:00
Makefile	update Intel copyright notices	2022-11-10 08:28:53 +00:00