From: Alberto Garcia <berto@igalia.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Alberto Garcia <berto@igalia.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH v7 0/4] Clean unused entries in the qcow2 L2/refcount cache
Date: Tue, 4 Aug 2015 15:14:38 +0300 [thread overview]
Message-ID: <cover.1438690126.git.berto@igalia.com> (raw)
v7:
- Rebase against the current master.
- Update version number in the 'since' field of the
'cache-clean-interval' option.
v6: https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg01929.html
- Update documentation to clarify what "unused entries" mean.
v5: https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg00573.html
- Fix build in mingw.
- Use getpagesize() instead of sysconf(_SC_PAGESIZE).
- Clarify that 0 is the default value for 'cache-clean-interval', and that
it disables the feature.
- Add the patch that documents how to configure the cache to this
series, expanded with the explanation of 'cache-clean-interval'.
(previous version:
https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg02253.html)
v4: https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg06120.html
- Revert the 'cache-clean-interval' change. This should probably go
into a new BlockDeviceInfoSpecific struct (along with other
settings), but is out of the scope for this series.
v3: https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg05473.html
- Add 'cache-clean-interval' field to ImageInfoSpecificQCow2.
v2: https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg05316.html
- Clarify that the block-commit mentioned in the first patch refers to
the HMP commit command.
- Check the value of cache_clean_interval and cast it accordingly to
prevent it from overflowing.
v1: https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg03510.html
Alberto Garcia (4):
qcow2: mark the memory as no longer needed after qcow2_cache_empty()
qcow2: add option to clean unused cache entries after some time
docs: document how to configure the qcow2 L2/refcount caches
qcow2: reorder fields in Qcow2CachedTable to reduce padding
block/qcow2-cache.c | 63 +++++++++++++++++++-
block/qcow2.c | 64 ++++++++++++++++++++
block/qcow2.h | 4 ++
docs/qcow2-cache.txt | 164 +++++++++++++++++++++++++++++++++++++++++++++++++++
qapi/block-core.json | 7 ++-
5 files changed, 300 insertions(+), 2 deletions(-)
create mode 100644 docs/qcow2-cache.txt
--
2.4.6
next reply other threads:[~2015-08-04 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 12:14 Alberto Garcia [this message]
2015-08-04 12:14 ` [Qemu-devel] [PATCH v7 1/4] qcow2: mark the memory as no longer needed after qcow2_cache_empty() Alberto Garcia
2015-08-04 12:14 ` [Qemu-devel] [PATCH v7 2/4] qcow2: add option to clean unused cache entries after some time Alberto Garcia
2015-08-04 12:14 ` [Qemu-devel] [PATCH v7 3/4] docs: document how to configure the qcow2 L2/refcount caches Alberto Garcia
2015-08-04 12:14 ` [Qemu-devel] [PATCH v7 4/4] qcow2: reorder fields in Qcow2CachedTable to reduce padding Alberto Garcia
2015-08-24 20:12 ` [Qemu-devel] [PATCH v7 0/4] Clean unused entries in the qcow2 L2/refcount cache Max Reitz
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=cover.1438690126.git.berto@igalia.com \
--to=berto@igalia.com \
--cc=kwolf@redhat.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 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.