diff options
| author | Lin Ma <lma@suse.com> | 2021-09-13 17:06:59 +0800 |
|---|---|---|
| committer | wanchao-xu <wanchao.xu@samsung.com> | 2024-01-09 19:57:13 +0800 |
| commit | 9de9b4521d3d4ef6fc1178e1910465c091214118 (patch) | |
| tree | a24922e222df738e1b8595dc6e31c9a7d47adcad /include/exec/memory.h | |
| parent | 98fe46fd23c27298aca8c5cb17a6c9ee5d6f4df0 (diff) | |
| download | qemu-arm-static-9de9b4521d3d4ef6fc1178e1910465c091214118.tar.gz qemu-arm-static-9de9b4521d3d4ef6fc1178e1910465c091214118.tar.bz2 qemu-arm-static-9de9b4521d3d4ef6fc1178e1910465c091214118.zip | |
scsi-generic: pass max_segments via max_iov field in BlockLimits
Git-commit: 01ef8185b809af9d287e1a03a3f9d8ea8231118a
References: bsc#1190425
I/O to a disk via read/write is not limited by the number of segments allowed
by the host adapter; the kernel can split requests if needed, and the limit
imposed by the host adapter can be very low (256k or so) to avoid that SG_IO
returns EINVAL if memory is heavily fragmented.
Since this value is only interesting for SG_IO-based I/O, do not include
it in the max_transfer and only take it into account when patching the
block limits VPD page in the scsi-generic device.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Signed-off-by: Lin Ma <lma@suse.com>
Diffstat (limited to 'include/exec/memory.h')
0 files changed, 0 insertions, 0 deletions