public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Reiter <s.reiter@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH INFO v2 qemu 4/5] PVE: increase max IOV count in QEMUFile
Date: Thu, 11 Feb 2021 17:11:14 +0100	[thread overview]
Message-ID: <20210211161115.15209-4-s.reiter@proxmox.com> (raw)
In-Reply-To: <20210211161115.15209-1-s.reiter@proxmox.com>

might help with RBD performance for snapshots, since it writes larger
data buffers at once

Signed-off-by: Stefan Reiter <s.reiter@proxmox.com>
---

Included in first patch, squashed into existing patches.
New in v2.

 migration/qemu-file.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/migration/qemu-file.c b/migration/qemu-file.c
index a4d2e2c8ff..1926b5202c 100644
--- a/migration/qemu-file.c
+++ b/migration/qemu-file.c
@@ -31,7 +31,7 @@
 #include "qapi/error.h"
 
 #define DEFAULT_IO_BUF_SIZE 32768
-#define MAX_IOV_SIZE MIN_CONST(IOV_MAX, 64)
+#define MAX_IOV_SIZE MIN_CONST(IOV_MAX, 256)
 
 struct QEMUFile {
     const QEMUFileOps *ops;
-- 
2.20.1





  parent reply	other threads:[~2021-02-11 16:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 16:11 [pve-devel] [PATCH v2 pve-qemu 1/5] Update to QEMU 5.2 Stefan Reiter
2021-02-11 16:11 ` [pve-devel] [PATCH v2 pve-qemu 2/5] add PBS master key support Stefan Reiter
2021-02-12 14:35   ` [pve-devel] applied: " Thomas Lamprecht
2021-02-11 16:11 ` [pve-devel] [PATCH INFO v2 qemu 3/5] PVE: Use coroutine QMP for backup/cancel_backup Stefan Reiter
2021-02-11 16:11 ` Stefan Reiter [this message]
2021-02-11 16:11 ` [pve-devel] [PATCH INFO v2 qemu 5/5] PVE: savevm-async: improve snapshot abort Stefan Reiter
2021-02-12 14:35 ` [pve-devel] applied: [PATCH v2 pve-qemu 1/5] Update to QEMU 5.2 Thomas Lamprecht

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=20210211161115.15209-4-s.reiter@proxmox.com \
    --to=s.reiter@proxmox.com \
    --cc=pve-devel@lists.proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal