[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [PATCHv4 0/4] introduce max_transfer_length
From: |
Peter Lieven |
Subject: |
[Qemu-devel] [PATCHv4 0/4] introduce max_transfer_length |
Date: |
Thu, 16 Oct 2014 09:54:46 +0200 |
This series adds the basics for introducing a maximum transfer length
to the block layer. Its main purpose is currently avoiding that
a multiwrite_merge exceeds the max_xfer_len of an attached iSCSI LUN.
This is a required bug fix.
Splitting up requests according to the max_transfer_length will follow
in a later series.
v3->v4: introduce MIN_NON_ZERO to correctly calculate minimum of 2 limits.
v2->v3: remove Patch 2 completely [Paolo]
v1->v2: do not throw errors but generate trace events in Patch 2 [Paolo]
Peter Lieven (4):
util: introduce MIN_NON_ZERO
BlockLimits: introduce max_transfer_length
block/iscsi: set max_transfer_length
block: avoid creating oversized writes in multiwrite_merge
block.c | 9 +++++++++
block/iscsi.c | 12 ++++++++++--
include/block/block_int.h | 3 +++
include/qemu/osdep.h | 4 ++++
4 files changed, 26 insertions(+), 2 deletions(-)
--
1.7.9.5
- [Qemu-devel] [PATCHv4 0/4] introduce max_transfer_length,
Peter Lieven <=