From: Peter Lieven <pl@kamp.de>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com, Peter Lieven <pl@kamp.de>,
mreitz@redhat.com, ronniesahlberg@gmail.com, pbonzini@redhat.com
Subject: [Qemu-devel] [PATCHv4 0/4] introduce max_transfer_length
Date: Thu, 16 Oct 2014 09:54:46 +0200 [thread overview]
Message-ID: <1413446090-30050-1-git-send-email-pl@kamp.de> (raw)
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
next reply other threads:[~2014-10-16 7:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 7:54 Peter Lieven [this message]
2014-10-16 7:54 ` [Qemu-devel] [PATCHv4 1/4] util: introduce MIN_NON_ZERO Peter Lieven
2014-10-22 22:34 ` Eric Blake
2014-10-23 10:10 ` Max Reitz
2014-10-16 7:54 ` [Qemu-devel] [PATCHv4 2/4] BlockLimits: introduce max_transfer_length Peter Lieven
2014-10-23 11:10 ` Max Reitz
2014-10-16 7:54 ` [Qemu-devel] [PATCHv4 3/4] block/iscsi: set max_transfer_length Peter Lieven
2014-10-23 11:18 ` Max Reitz
2014-10-25 15:16 ` Peter Lieven
2014-10-27 8:16 ` Max Reitz
2014-10-16 7:54 ` [Qemu-devel] [PATCHv4 4/4] block: avoid creating oversized writes in multiwrite_merge Peter Lieven
2014-10-23 11:23 ` Max Reitz
2014-10-25 15:19 ` Peter Lieven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1413446090-30050-1-git-send-email-pl@kamp.de \
--to=pl@kamp.de \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).