qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Timo Grodzinski <t.grodzinski@profihost.ag>
Subject: [Qemu-devel] drive-backup
Date: Mon, 22 Feb 2016 21:21:22 +0100	[thread overview]
Message-ID: <56CB6DC2.8040106@profihost.ag> (raw)

Hello,

is there any chance or hack to work with a bigger cluster size for the 
drive backup job?

See:
http://git.qemu.org/?p=qemu.git;a=blob;f=block/backup.c;h=16105d40b193be9bb40346027bdf58e62b956a96;hb=98d2c6f2cd80afaa2dc10091f5e35a97c181e4f5

This is very slow with ceph - may be due to the 64k block size. I would 
like to check whether this is faster with cephs native block size of 4mb.

Greets,
Stefan

             reply	other threads:[~2016-02-22 20:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 20:21 Stefan Priebe [this message]
2016-02-22 22:08 ` [Qemu-devel] drive-backup John Snow
2016-02-25  7:49   ` Stefan Priebe - Profihost AG
2016-02-25  7:59     ` Fam Zheng
2016-02-25 19:53     ` John Snow
2016-02-26  8:56       ` Stefan Priebe

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=56CB6DC2.8040106@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=qemu-devel@nongnu.org \
    --cc=t.grodzinski@profihost.ag \
    /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).