qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PULL 04/10] block: replace IOV_MAX with BlockLimits.max_iov
Date: Tue, 22 Dec 2015 16:54:14 +0800	[thread overview]
Message-ID: <1450774460-17259-5-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1450774460-17259-1-git-send-email-stefanha@redhat.com>

Request merging must not result in a huge request that exceeds the
maximum number of iovec elements.  Use BlockLimits.max_iov instead of
hardcoding IOV_MAX.

Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
 block/io.c            | 3 ++-
 hw/block/virtio-blk.c | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/block/io.c b/block/io.c
index 42050a0..63e3678 100644
--- a/block/io.c
+++ b/block/io.c
@@ -1889,7 +1889,8 @@ static int multiwrite_merge(BlockDriverState *bs, BlockRequest *reqs,
             merge = 1;
         }
 
-        if (reqs[outidx].qiov->niov + reqs[i].qiov->niov + 1 > IOV_MAX) {
+        if (reqs[outidx].qiov->niov + reqs[i].qiov->niov + 1 >
+            bs->bl.max_iov) {
             merge = 0;
         }
 
diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
index f72d4b6..51f867b 100644
--- a/hw/block/virtio-blk.c
+++ b/hw/block/virtio-blk.c
@@ -414,7 +414,7 @@ void virtio_blk_submit_multireq(BlockBackend *blk, MultiReqBuffer *mrb)
              * 3. merge would exceed maximum transfer length of backend device
              */
             if (sector_num + nb_sectors != req->sector_num ||
-                niov > IOV_MAX - req->qiov.niov ||
+                niov > blk_get_max_iov(blk) - req->qiov.niov ||
                 req->qiov.size / BDRV_SECTOR_SIZE > max_xfer_len ||
                 nb_sectors > max_xfer_len - req->qiov.size / BDRV_SECTOR_SIZE) {
                 submit_requests(blk, mrb, start, num_reqs, niov);
-- 
2.5.0

  parent reply	other threads:[~2015-12-22  8:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22  8:54 [Qemu-devel] [PULL 00/10] Block patches Stefan Hajnoczi
2015-12-22  8:54 ` [Qemu-devel] [PULL 01/10] virtio-blk: trivial code optimization Stefan Hajnoczi
2015-12-22  8:54 ` [Qemu-devel] [PULL 02/10] block: add BlockLimits.max_iov field Stefan Hajnoczi
2015-12-22  8:54 ` [Qemu-devel] [PULL 03/10] block-backend: add blk_get_max_iov() Stefan Hajnoczi
2015-12-22  8:54 ` Stefan Hajnoczi [this message]
2015-12-22  8:54 ` [Qemu-devel] [PULL 05/10] block/mirror: replace IOV_MAX with blk_get_max_iov() Stefan Hajnoczi
2015-12-22  8:54 ` [Qemu-devel] [PULL 06/10] parallels: add format spec Stefan Hajnoczi
2015-12-22  8:54 ` [Qemu-devel] [PULL 07/10] scripts/gdb: Fix a python exception in mtree.py Stefan Hajnoczi
2015-12-22  8:54 ` [Qemu-devel] [PULL 08/10] sd: sdhci: Delete over-zealous power check Stefan Hajnoczi
2015-12-22  8:54 ` [Qemu-devel] [PULL 09/10] sdhci: don't raise a command index error for an unexpected response Stefan Hajnoczi
2015-12-22  8:54 ` [Qemu-devel] [PULL 10/10] sdhci: add optional quirk property to disable card insertion/removal interrupts Stefan Hajnoczi
2015-12-22 14:47 ` [Qemu-devel] [PULL 00/10] Block patches Peter Maydell

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=1450774460-17259-5-git-send-email-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).