From: Avi Kivity <avi@redhat.com>
To: OHMURA Kei <ohmura.kei@lab.ntt.co.jp>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] qemu-kvm: Speed up of the dirty-bitmap-traveling
Date: Mon, 08 Feb 2010 14:40:59 +0200 [thread overview]
Message-ID: <4B70065B.1010401@redhat.com> (raw)
In-Reply-To: <4B6BF06D.1090909@lab.ntt.co.jp>
On 02/05/2010 12:18 PM, OHMURA Kei wrote:
> dirty-bitmap-traveling is carried out by byte size in qemu-kvm.c.
> But We think that dirty-bitmap-traveling by long size is faster than by byte
> size especially when most of memory is not dirty.
>
>
>
> +
> +static int kvm_get_dirty_pages_log_range_by_long(unsigned long start_addr,
> + unsigned char *bitmap,
> + unsigned long offset,
> + unsigned long mem_size)
> +{
> + unsigned int i;
> + unsigned int len;
> + unsigned long *bitmap_ul = (unsigned long *)bitmap;
> +
> + /* bitmap-traveling by long size is faster than by byte size
> + * especially when most of memory is not dirty.
> + * bitmap should be long-size aligned for traveling by long.
> + */
> + if (((unsigned long)bitmap & (TARGET_LONG_SIZE - 1)) == 0) {
>
Since we allocate the bitmap, we can be sure that it is aligned on a
long boundary (qemu_malloc() should guarantee that). So you can
eliminate the fallback.
> + len = ((mem_size / TARGET_PAGE_SIZE) + TARGET_LONG_BITS - 1) /
> + TARGET_LONG_BITS;
> + for (i = 0; i < len; i++)
> + if (bitmap_ul[i] != 0)
> + kvm_get_dirty_pages_log_range_by_byte(i * TARGET_LONG_SIZE,
> + (i + 1) * TARGET_LONG_SIZE, bitmap, offset);
>
Better to just use the original loop here (since we don't need the
function as a fallback).
> + /*
> + * We will check the remaining dirty-bitmap,
> + * when the mem_size is not a multiple of TARGET_LONG_SIZE.
> + */
> + if ((mem_size & (TARGET_LONG_SIZE - 1)) != 0) {
> + len = ((mem_size / TARGET_PAGE_SIZE) + 7) / 8;
> + kvm_get_dirty_pages_log_range_by_byte(i * TARGET_LONG_SIZE,
> + len, bitmap, offset);
> + }
>
Seems like the bitmap size is also aligned as well (allocated using
BITMAP_SIZE which aligns using HOST_LONG_BITS), so this is unnecessary
as well.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-02-08 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 10:18 [PATCH] qemu-kvm: Speed up of the dirty-bitmap-traveling OHMURA Kei
2010-02-05 12:04 ` Jan Kiszka
2010-02-08 6:14 ` OHMURA Kei
2010-02-08 11:23 ` OHMURA Kei
2010-02-08 11:44 ` Jan Kiszka
2010-02-09 9:55 ` OHMURA Kei
2010-02-08 12:40 ` Avi Kivity [this message]
2010-02-09 9:54 ` OHMURA Kei
2010-02-09 10:26 ` Avi Kivity
2010-02-10 9:55 ` OHMURA Kei
2010-02-10 10:24 ` Avi Kivity
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=4B70065B.1010401@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=ohmura.kei@lab.ntt.co.jp \
--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