From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: berto@igalia.com, qemu-block@nongnu.org, kwolf@redhat.com
Subject: [Qemu-devel] [PATCH v4 0/5] minor compression improvements
Date: Tue, 27 Feb 2018 09:55:09 -0600 [thread overview]
Message-ID: <20180227155514.16721-1-eblake@redhat.com> (raw)
In v4:
- patch 2 has even more wording tweaks [Kevin]
- patch 3 is new [Berto]
- patch 5 fixes an off-by-one [Berto]
Eric Blake (5):
qcow2: Prefer byte-based calls into bs->file
qcow2: Document some maximum size constraints
qcow2: Reduce REFT_OFFSET_MASK
qcow2: Don't allow overflow during cluster allocation
qcow2: Avoid memory over-allocation on compressed images
docs/interop/qcow2.txt | 38 +++++++++++++++++++++++++++++++++++---
block/qcow2.h | 8 +++++++-
block/qcow2-cluster.c | 32 ++++++++++++++++++++------------
block/qcow2-refcount.c | 27 +++++++++++++++++----------
block/qcow2.c | 2 +-
5 files changed, 80 insertions(+), 27 deletions(-)
--
2.14.3
next reply other threads:[~2018-02-27 15:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 15:55 Eric Blake [this message]
2018-02-27 16:29 ` [Qemu-devel] [PATCH v4 1/5] qcow2: Prefer byte-based calls into bs->file Eric Blake
2018-02-27 16:29 ` [Qemu-devel] [PATCH v4 2/5] qcow2: Document some maximum size constraints Eric Blake
2018-02-28 10:26 ` Alberto Garcia
2018-02-28 14:01 ` Eric Blake
2018-02-28 14:20 ` Alberto Garcia
2018-04-13 17:08 ` Max Reitz
2018-04-18 13:49 ` Eric Blake
2018-02-27 16:29 ` [Qemu-devel] [PATCH v4 3/5] qcow2: Reduce REFT_OFFSET_MASK Eric Blake
2018-02-28 12:18 ` Alberto Garcia
2018-02-27 16:29 ` [Qemu-devel] [PATCH v4 4/5] qcow2: Don't allow overflow during cluster allocation Eric Blake
2018-02-27 16:29 ` [Qemu-devel] [PATCH v4 5/5] qcow2: Avoid memory over-allocation on compressed images Eric Blake
2018-02-28 14:22 ` Alberto Garcia
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=20180227155514.16721-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=berto@igalia.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).