From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Khoa Huynh <khoa@us.ibm.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 3/7] docs: add lazy refcounts bit to qcow2 specification
Date: Thu, 26 Jul 2012 14:57:20 +0200 [thread overview]
Message-ID: <50113EB0.7070709@redhat.com> (raw)
In-Reply-To: <1343218884-14980-4-git-send-email-stefanha@linux.vnet.ibm.com>
Am 25.07.2012 14:21, schrieb Stefan Hajnoczi:
> The lazy refcounts bit indicates that this image can take advantage of
> the dirty bit and that refcount updates can be postponed.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
> ---
> docs/specs/qcow2.txt | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/docs/specs/qcow2.txt b/docs/specs/qcow2.txt
> index 339cdc1..f2f4faa 100644
> --- a/docs/specs/qcow2.txt
> +++ b/docs/specs/qcow2.txt
> @@ -86,7 +86,12 @@ in the description of a field.
> Bitmask of compatible features. An implementation can
> safely ignore any unknown bits that are set.
>
> - Bits 0-63: Reserved (set to 0)
> + Bit 0: Lazy refcounts bit. If this bit is set then
> + lazy refcount updates can be used. This means
> + postponing marking the image file dirty and
Not sure what was intended here, but the dirty flag isn't set anywhere
yet, so you can't postpone it either. Maybe s/postponing//?
> + postponing refcount metadata updates.
> +
> + Bits 1-63: Reserved (set to 0)
>
> 88 - 95: autoclear_features
> Bitmask of auto-clear features. An implementation may only
Kevin
next prev parent reply other threads:[~2012-07-26 12:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 12:21 [Qemu-devel] [PATCH v2 0/7] qcow2: implement lazy refcounts optimization Stefan Hajnoczi
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 1/7] docs: add dirty bit to qcow2 specification Stefan Hajnoczi
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 2/7] qcow2: introduce dirty bit Stefan Hajnoczi
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 3/7] docs: add lazy refcounts bit to qcow2 specification Stefan Hajnoczi
2012-07-26 12:57 ` Kevin Wolf [this message]
2012-07-26 15:36 ` Stefan Hajnoczi
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 4/7] qemu-iotests: ignore qemu-img create lazy_refcounts output Stefan Hajnoczi
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 5/7] qcow2: implement lazy refcounts Stefan Hajnoczi
2012-07-26 13:15 ` Kevin Wolf
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 6/7] qemu-io: add "abort" command to simulate program crash Stefan Hajnoczi
2012-07-25 12:21 ` [Qemu-devel] [PATCH v2 7/7] qemu-iotests: add 039 qcow2 lazy refcounts test Stefan Hajnoczi
2012-07-25 17:54 ` Eric Blake
2012-07-25 22:45 ` Stefan Hajnoczi
2012-07-25 23:41 ` Eric Blake
2012-07-26 13:28 ` Kevin Wolf
2012-07-27 7:56 ` Stefan Hajnoczi
2012-07-27 8:07 ` Kevin Wolf
2012-07-30 10:09 ` Stefan Hajnoczi
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=50113EB0.7070709@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=khoa@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.