qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: corentincj@iksaif.net, hengqing.hu@gmail.com, anthony@codemonkey.ws
Subject: Re: [Qemu-devel] [PATCHv2 3/6] ui/vnc: optimize dirty bitmap tracking
Date: Thu, 21 Nov 2013 08:16:29 -0700	[thread overview]
Message-ID: <528E23CD.1090308@redhat.com> (raw)
In-Reply-To: <1385023877-26524-4-git-send-email-pl@kamp.de>

[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]

On 11/21/2013 01:51 AM, Peter Lieven wrote:
> vnc_update_client currently scans the dirty bitmap of each client
> bitwise which is a very costly operation if only few bits are dirty.
> vnc_refresh_server_surface does almost the same.
> this patch optimizes both by utilizing the heavily optimized
> function find_next_bit to find the offset of the next dirty
> bit in the dirty bitmaps.
> 
> The following artifical test (just the bitmap operation part) running

s/artifical/artificial/

> vnc_update_client 65536 times on a 2560x2048 surface illustrates the
> performance difference:
> 
> All bits clean - vnc_update_client_new: 0.07 secs
>                  vnc_update_client_old: 10.98 secs
> 
> All bits dirty - vnc_update_client_new: 11.26 secs
>                  vnc_update_client_old: 20.19 secs
> 
> Few bits dirty - vnc_update_client_new: 0.08 secs
>                  vnc_update_client_old: 10.98 secs
> 
> The case for all bits dirty is still rather slow, this
> is due to the implementation of find_and_clear_dirty_height.
> This will be addresses in a separate patch.

s/addresses/addressed/

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

  reply	other threads:[~2013-11-21 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21  8:51 [Qemu-devel] [PATCHv2 0/6] ui/vnc: update optimizations Peter Lieven
2013-11-21  8:51 ` [Qemu-devel] [PATCHv2 1/6] ui/vnc: introduce VNC_DIRTY_PIXELS_PER_BIT macro Peter Lieven
2013-11-21  8:51 ` [Qemu-devel] [PATCHv2 2/6] ui/vnc: derive cmp_bytes from VNC_DIRTY_PIXELS_PER_BIT Peter Lieven
2013-11-21  8:51 ` [Qemu-devel] [PATCHv2 3/6] ui/vnc: optimize dirty bitmap tracking Peter Lieven
2013-11-21 15:16   ` Eric Blake [this message]
2013-11-21  8:51 ` [Qemu-devel] [PATCHv2 4/6] ui/vnc: optimize clearing in find_and_clear_dirty_height() Peter Lieven
2013-11-21  8:51 ` [Qemu-devel] [PATCHv2 5/6] ui/vnc: optimize setting in vnc_dpy_update() Peter Lieven
2013-11-21  8:51 ` [Qemu-devel] [PATCHv2 6/6] ui/vnc: disable adaptive update calculations if not needed Peter Lieven
2013-12-04 17:56 ` [Qemu-devel] RESEND: [PATCHv2 0/6] ui/vnc: update optimizations Peter Lieven
2013-12-04 18:20   ` Stefan Weil
2013-12-04 21:04     ` Peter Lieven

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=528E23CD.1090308@redhat.com \
    --to=eblake@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=corentincj@iksaif.net \
    --cc=hengqing.hu@gmail.com \
    --cc=pl@kamp.de \
    --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).