From: Laurent Vivier <Laurent.Vivier@bull.net>
To: Shahar Frank <shaharf@qumranet.com>
Cc: Kevin Wolf <kwolf@suse.de>, qemu-devel@nongnu.org
Subject: RE: [Qemu-devel][PATCH,RFC] Zero cluster dedup
Date: Wed, 03 Sep 2008 15:12:38 +0200 [thread overview]
Message-ID: <1220447558.4189.22.camel@frecb07144> (raw)
In-Reply-To: <ED2414DB5FBBCF4FA66ECE71F290E9A29B81E0@EXVBE011-2.exch011.intermedia.net>
Le mercredi 03 septembre 2008 à 06:07 -0700, Shahar Frank a écrit :
> > This is still the L2 table which has to be written each time. Say we
> > have a 64k write, then you could save 15 L2 table writes if qcow_dedup
> > could handle zeroing multiple contiguous clusters at once. This could
> > matter for performance when wiping lots of data.
>
> You have a good point when it comes to a sequence of zero clusters (the
> L2 writes can be optimized as you wrote above). I will re-implement
> this.
Perhaps you should consider to set the l2_table entry to 0 when there is
no backing file: it avoids some I/O and allows to aggregate free
entries.
(no, I'm not obstinate :-D )
Laurent
--
----------------- Laurent.Vivier@bull.net ------------------
"La perfection est atteinte non quand il ne reste rien à
ajouter mais quand il ne reste rien à enlever." Saint Exupéry
next prev parent reply other threads:[~2008-09-03 13:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 16:28 [Qemu-devel][PATCH,RFC] Zero cluster dedup Shahar Frank
2008-09-03 7:09 ` Laurent Vivier
2008-09-03 7:35 ` Shahar Frank
2008-09-03 7:59 ` Laurent Vivier
2008-09-03 8:13 ` Kevin Wolf
2008-09-03 8:25 ` Laurent Vivier
2008-09-03 9:38 ` Kevin Wolf
2008-09-03 12:05 ` Shahar Frank
2008-09-03 12:47 ` Kevin Wolf
2008-09-03 13:07 ` Shahar Frank
2008-09-03 13:12 ` Laurent Vivier [this message]
2008-09-03 17:44 ` Shahar Frank
2008-09-03 13:09 ` Laurent Vivier
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=1220447558.4189.22.camel@frecb07144 \
--to=laurent.vivier@bull.net \
--cc=kwolf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=shaharf@qumranet.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).