From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Alberto Garcia <berto@igalia.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [RFC] Proposed qcow2 extension: subcluster allocation
Date: Mon, 10 Apr 2017 10:42:50 +0200 [thread overview]
Message-ID: <20170410084250.GC4883@noname.redhat.com> (raw)
In-Reply-To: <d60ea1f9-ae2c-6625-90de-944cbb490f85@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
Am 07.04.2017 um 19:10 hat Max Reitz geschrieben:
> One case I'd be especially interested in are of course 4 kB subclusters
> for 64 kB clusters (because 4 kB is a usual page size and can be
> configured to be the block size of a guest device; and because 64 kB
> simply is the standard cluster size of qcow2 images nowadays[1]...).
Why should the current default cluster size be an argument for anything?
64k is a tradeoff between small COW size and large allocation
granularity that seemed to work well (and it used to be the maximum
cluster size originally, so it seemed safer than 128k).
With subclusters, we have a completely different situation and need to
find a new default that works best. I'm relatively sure that 64k are too
small under the new conditions.
Also, undefined reference: [1] (I was hoping to find a better argument
there...)
Kevin
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2017-04-10 8:43 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 15:01 [Qemu-devel] [RFC] Proposed qcow2 extension: subcluster allocation Alberto Garcia
2017-04-06 16:40 ` Eric Blake
2017-04-07 8:49 ` Alberto Garcia
2017-04-07 12:41 ` Kevin Wolf
2017-04-07 14:24 ` Alberto Garcia
2017-04-21 21:09 ` [Qemu-devel] proposed qcow2 extension: cluster reservations [was: " Eric Blake
2017-04-22 17:56 ` Max Reitz
2017-04-24 11:45 ` Kevin Wolf
2017-04-24 12:46 ` Alberto Garcia
2017-04-07 12:20 ` [Qemu-devel] " Stefan Hajnoczi
2017-04-07 12:24 ` Alberto Garcia
2017-04-07 13:01 ` Kevin Wolf
2017-04-10 15:32 ` Stefan Hajnoczi
2017-04-07 17:10 ` Max Reitz
2017-04-10 8:42 ` Kevin Wolf [this message]
2017-04-10 15:03 ` Max Reitz
2017-04-11 12:56 ` Alberto Garcia
2017-04-11 14:04 ` Max Reitz
2017-04-11 14:31 ` Alberto Garcia
2017-04-11 14:45 ` [Qemu-devel] [Qemu-block] " Eric Blake
2017-04-12 12:41 ` Alberto Garcia
2017-04-12 14:10 ` Max Reitz
2017-04-13 8:05 ` Alberto Garcia
2017-04-13 9:02 ` Kevin Wolf
2017-04-13 9:05 ` Alberto Garcia
2017-04-11 14:49 ` [Qemu-devel] " Kevin Wolf
2017-04-11 14:58 ` Eric Blake
2017-04-11 14:59 ` Max Reitz
2017-04-11 15:08 ` Eric Blake
2017-04-11 15:18 ` Max Reitz
2017-04-11 15:29 ` Kevin Wolf
2017-04-11 15:29 ` Max Reitz
2017-04-11 15:30 ` Eric Blake
2017-04-11 15:34 ` Max Reitz
2017-04-12 12:47 ` Alberto Garcia
2017-04-12 16:54 ` Denis V. Lunev
2017-04-13 11:58 ` Alberto Garcia
2017-04-13 12:44 ` Denis V. Lunev
2017-04-13 13:05 ` Kevin Wolf
2017-04-13 13:09 ` Denis V. Lunev
2017-04-13 13:36 ` Alberto Garcia
2017-04-13 14:06 ` Denis V. Lunev
2017-04-13 13:21 ` Alberto Garcia
2017-04-13 13:30 ` Denis V. Lunev
2017-04-13 13:59 ` Kevin Wolf
2017-04-13 15:04 ` Alberto Garcia
2017-04-13 15:17 ` Denis V. Lunev
2017-04-18 11:52 ` Alberto Garcia
2017-04-18 17:27 ` Denis V. Lunev
2017-04-13 13:51 ` Kevin Wolf
2017-04-13 14:15 ` Alberto Garcia
2017-04-13 14:27 ` Kevin Wolf
2017-04-13 16:42 ` [Qemu-devel] [Qemu-block] " Roman Kagan
2017-04-13 14:42 ` [Qemu-devel] " Denis V. Lunev
2017-04-12 17:55 ` Denis V. Lunev
2017-04-12 18:20 ` Eric Blake
2017-04-12 19:02 ` Denis V. Lunev
2017-04-13 9:44 ` Kevin Wolf
2017-04-13 10:19 ` Denis V. Lunev
2017-04-14 1:06 ` [Qemu-devel] [Qemu-block] " John Snow
2017-04-14 4:17 ` Denis V. Lunev
2017-04-18 11:22 ` Kevin Wolf
2017-04-18 17:30 ` Denis V. Lunev
2017-04-14 7:40 ` Roman Kagan
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=20170410084250.GC4883@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=berto@igalia.com \
--cc=mreitz@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).