From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, famz@redhat.com, qemu-block@nongnu.org,
stefanha@redhat.com
Subject: [Qemu-devel] [PATCH v3 0/6] Auto-fragment large transactions at the block layer
Date: Fri, 15 Jul 2016 12:31:58 -0600 [thread overview]
Message-ID: <1468607524-19021-1-git-send-email-eblake@redhat.com> (raw)
We have max_transfer documented in BlockLimits, but while we
honor it during pwrite_zeroes, we were blindly ignoring it
during pwritev and preadv, leading to multiple drivers having
to implement fragmentation themselves. This series moves
fragmentation to the block layer, then fixes the NBD and iscsi
driver to use it.
qcow2 still does self-fragmenting, but that's because of cluster
boundaries where it really has to do additional work beyond what
the block layer can automatically provide.
Prequisite: Kevin's latest block branch PULL request
Also available as a tag at:
git fetch git://repo.or.cz/qemu/ericb.git nbd-fragment-v3
Changes since v2:
- patch 1, 3: change return semantics to be 0, not bytes, on success,
since at least one caller asserts during 'make check' otherwise
001/6:[0008] [FC] 'block: Fragment reads to max transfer length'
002/6:[----] [--] 'raw_bsd: Don't advertise flags not supported by protocol layer'
003/6:[0002] [FC] 'block: Fragment writes to max transfer length'
004/6:[----] [--] 'nbd: Rely on block layer to break up large requests'
005/6:[----] [--] 'nbd: Drop unused offset parameter'
006/6:[----] [--] 'iscsi: Rely on block layer to break up large requests'
Eric Blake (6):
block: Fragment reads to max transfer length
raw_bsd: Don't advertise flags not supported by protocol layer
block: Fragment writes to max transfer length
nbd: Rely on block layer to break up large requests
nbd: Drop unused offset parameter
iscsi: Rely on block layer to break up large requests
include/block/nbd.h | 1 -
nbd/nbd-internal.h | 4 +--
block/io.c | 90 +++++++++++++++++++++++++++++++++++++++--------------
block/iscsi.c | 14 +++------
block/nbd-client.c | 78 +++++++++++++---------------------------------
block/nbd.c | 12 ++-----
block/raw_bsd.c | 6 ++--
nbd/common.c | 5 +--
8 files changed, 103 insertions(+), 107 deletions(-)
--
2.5.5
next reply other threads:[~2016-07-15 18:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 18:31 Eric Blake [this message]
2016-07-15 18:31 ` [Qemu-devel] [PATCH v3 1/6] block: Fragment reads to max transfer length Eric Blake
2016-07-15 18:32 ` [Qemu-devel] [PATCH v3 2/6] raw_bsd: Don't advertise flags not supported by protocol layer Eric Blake
2016-07-15 18:32 ` [Qemu-devel] [PATCH v3 3/6] block: Fragment writes to max transfer length Eric Blake
2016-07-15 18:32 ` [Qemu-devel] [PATCH v3 4/6] nbd: Rely on block layer to break up large requests Eric Blake
2016-07-18 8:16 ` Paolo Bonzini
2016-07-15 18:32 ` [Qemu-devel] [PATCH v3 5/6] nbd: Drop unused offset parameter Eric Blake
2016-07-18 8:16 ` Paolo Bonzini
2016-07-15 18:32 ` [Qemu-devel] [PATCH v3 6/6] iscsi: Rely on block layer to break up large requests Eric Blake
2016-07-18 8:16 ` Paolo Bonzini
2016-07-19 16:12 ` [Qemu-devel] [PATCH v3 0/6] Auto-fragment large transactions at the block layer Stefan Hajnoczi
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=1468607524-19021-1-git-send-email-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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).