qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: 858585 jemmy <jemmy858585@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu block <qemu-block@nongnu.org>,
	Juan Quintela <quintela@redhat.com>,
	Dave Gilbert <dgilbert@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Lidong Chen <lidongchen@tencent.com>
Subject: Re: [Qemu-devel] [PATCH v6] migration/block: use blk_pwrite_zeroes for each zero cluster
Date: Mon, 17 Apr 2017 12:00:58 +0800	[thread overview]
Message-ID: <CAOGPPbd_Y6m42EpuedngTWfGzt+MDvOwbPSmwp-OG5hVpMNBkA@mail.gmail.com> (raw)
In-Reply-To: <20170417034925.GC6717@lemon.lan>

On Mon, Apr 17, 2017 at 11:49 AM, Fam Zheng <famz@redhat.com> wrote:
> On Fri, 04/14 14:30, 858585 jemmy wrote:
>> Do you know some other format which have very small cluster size?
>
> 64k is the default cluster size for qcow2 but it can be configured at image
> creation time, as 512 bytes, for example:
>
>     $ qemu-img create -f qcow2 test.qcow2 -o cluster_size=512 1G

Thanks, i will test the performance again.
>
> Fam

  reply	other threads:[~2017-04-17  4:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13  2:34 [Qemu-devel] [PATCH v6] migration/block: use blk_pwrite_zeroes for each zero cluster jemmy858585
2017-04-13 14:16 ` Stefan Hajnoczi
2017-04-14  0:57   ` 858585 jemmy
2017-04-14  6:00 ` Fam Zheng
2017-04-14  6:30   ` 858585 jemmy
2017-04-17  3:49     ` Fam Zheng
2017-04-17  4:00       ` 858585 jemmy [this message]
2017-04-24  7:40         ` 858585 jemmy
2017-04-24 11:54           ` 858585 jemmy
2017-04-24 12:09             ` Fam Zheng
2017-04-24 12:15               ` 858585 jemmy
2017-04-24 12:19               ` Fam Zheng
2017-04-24 12:26                 ` 858585 jemmy
2017-04-24 12:36                   ` Fam Zheng
2017-04-24 12:44                     ` 858585 jemmy
2017-04-14  6:38   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-04-14  6:48     ` 858585 jemmy
2017-04-17  3:47       ` Fam Zheng

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=CAOGPPbd_Y6m42EpuedngTWfGzt+MDvOwbPSmwp-OG5hVpMNBkA@mail.gmail.com \
    --to=jemmy858585@gmail.com \
    --cc=dgilbert@redhat.com \
    --cc=famz@redhat.com \
    --cc=lidongchen@tencent.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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).