From: Stefan Hajnoczi <stefanha@redhat.com>
To: Zhang Haoyu <zhanghy@sangfor.com.cn>
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Fam Zheng <famz@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] optimization for qcow2 cache get/put
Date: Thu, 26 Mar 2015 14:33:58 +0000 [thread overview]
Message-ID: <20150326143358.GB630@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <201501262119592629551@sangfor.com.cn>
[-- Attachment #1: Type: text/plain, Size: 2710 bytes --]
On Mon, Jan 26, 2015 at 09:20:00PM +0800, Zhang Haoyu wrote:
> Hi, all
>
> Regarding too large qcow2 image, e.g., 2TB,
> so long disruption happened when performing snapshot,
> which was caused by cache update and IO wait.
I have CCed Kevin Wolf, the qcow2 maintainer.
> perf top data shown as below,
> PerfTop: 2554 irqs/sec kernel: 0.4% exact: 0.0% [4000Hz cycles], (target_pid: 34294)
> ------------------------------------------------------------------------------------------------------------------------
>
> 33.80% qemu-system-x86_64 [.] qcow2_cache_do_get
> 27.59% qemu-system-x86_64 [.] qcow2_cache_put
> 15.19% qemu-system-x86_64 [.] qcow2_cache_entry_mark_dirty
> 5.49% qemu-system-x86_64 [.] update_refcount
> 3.02% libpthread-2.13.so [.] pthread_getspecific
> 2.26% qemu-system-x86_64 [.] get_refcount
> 1.95% qemu-system-x86_64 [.] coroutine_get_thread_state
> 1.32% qemu-system-x86_64 [.] qcow2_update_snapshot_refcount
> 1.20% qemu-system-x86_64 [.] qemu_coroutine_self
> 1.16% libz.so.1.2.7 [.] 0x0000000000003018
> 0.95% qemu-system-x86_64 [.] qcow2_update_cluster_refcount
> 0.91% qemu-system-x86_64 [.] qcow2_cache_get
> 0.76% libc-2.13.so [.] 0x0000000000134e49
> 0.73% qemu-system-x86_64 [.] bdrv_debug_event
> 0.16% qemu-system-x86_64 [.] pthread_getspecific@plt
> 0.12% [kernel] [k] _raw_spin_unlock_irqrestore
> 0.10% qemu-system-x86_64 [.] vga_draw_line24_32
> 0.09% [vdso] [.] 0x000000000000060c
> 0.09% qemu-system-x86_64 [.] qcow2_check_metadata_overlap
> 0.08% [kernel] [k] do_blockdev_direct_IO
>
> If expand the cache table size, the IO will be decreased,
> but the calculation time will be grown.
> so it's worthy to optimize qcow2 cache get and put algorithm.
>
> My proposal:
> get:
> using ((use offset >> cluster_bits) % c->size) to locate the cache entry,
> raw implementation,
> index = (use offset >> cluster_bits) % c->size;
> if (c->entries[index].offset == offset) {
> goto found;
> }
>
> replace:
> c->entries[use offset >> cluster_bits) % c->size].offset = offset;
> ...
>
> put:
> using 64-entries cache table to cache
> the recently got c->entries, i.e., cache for cache,
> then during put process, firstly search the 64-entries cache,
> if not found, then the c->entries.
>
> Any idea?
>
> Thanks,
> Zhang Haoyu
>
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-03-26 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 13:20 [Qemu-devel] [RFC] optimization for qcow2 cache get/put Zhang Haoyu
2015-01-26 14:11 ` Max Reitz
2015-01-27 1:23 ` Zhang Haoyu
2015-01-27 3:53 ` Zhang Haoyu
2015-03-26 14:33 ` Stefan Hajnoczi [this message]
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=20150326143358.GB630@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhanghy@sangfor.com.cn \
/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).