From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Lieven <pl@kamp.de>, Gerd Hoffmann <kraxel@redhat.com>,
Anthony Liguori <aliguori@amazon.com>
Subject: [Qemu-devel] [PULL 7/9] ui/vnc: optimize clearing in find_and_clear_dirty_height()
Date: Mon, 10 Mar 2014 13:49:11 +0100 [thread overview]
Message-ID: <1394455753-13783-8-git-send-email-kraxel@redhat.com> (raw)
In-Reply-To: <1394455753-13783-1-git-send-email-kraxel@redhat.com>
From: Peter Lieven <pl@kamp.de>
The following artifical test (just the bitmap operation part) running
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_new2: 0.07 secs
vnc_update_client_old: 10.98 secs
All bits dirty - vnc_update_client_new: 11.26 secs
- vnc_update_client_new2: 0.29 secs
vnc_update_client_old: 20.19 secs
Few bits dirty - vnc_update_client_new: 0.07 secs
- vnc_update_client_new2: 0.07 secs
vnc_update_client_old: 10.98 secs
vnc_update_client_new2 shows the performance of vnc_update_client
with this patch added.
Comparing with the test run of the last patch the performance
is at least unchanged while it is significantly improved
for the all bits dirty case.
Signed-off-by: Peter Lieven <pl@kamp.de>
Reviewed-by: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
ui/vnc.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/ui/vnc.c b/ui/vnc.c
index 1ed360a..e1d6ca3 100644
--- a/ui/vnc.c
+++ b/ui/vnc.c
@@ -879,13 +879,10 @@ static int find_and_clear_dirty_height(struct VncState *vs,
int h;
for (h = 1; h < (height - y); h++) {
- int tmp_x;
if (!test_bit(last_x, vs->dirty[y + h])) {
break;
}
- for (tmp_x = last_x; tmp_x < x; tmp_x++) {
- clear_bit(tmp_x, vs->dirty[y + h]);
- }
+ bitmap_clear(vs->dirty[y + h], last_x, x - last_x);
}
return h;
--
1.8.3.1
next prev parent reply other threads:[~2014-03-10 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 12:49 [Qemu-devel] [PULL 0/9] vnc patches Gerd Hoffmann
2014-03-10 12:49 ` [Qemu-devel] [PULL 1/9] vnc: Fix tight_detect_smooth_image() for lossless case Gerd Hoffmann
2014-03-10 12:49 ` [Qemu-devel] [PULL 2/9] vnc: Fix qemu crashed when vnc client disconnect suddenly Gerd Hoffmann
2014-03-10 12:49 ` [Qemu-devel] [PULL 3/9] vnc: fix use-after-free in vnc_update_client_sync Gerd Hoffmann
2014-03-10 12:49 ` [Qemu-devel] [PULL 4/9] ui/vnc: introduce VNC_DIRTY_PIXELS_PER_BIT macro Gerd Hoffmann
2014-03-10 12:49 ` [Qemu-devel] [PULL 5/9] ui/vnc: derive cmp_bytes from VNC_DIRTY_PIXELS_PER_BIT Gerd Hoffmann
2014-03-10 12:49 ` [Qemu-devel] [PULL 6/9] ui/vnc: optimize dirty bitmap tracking Gerd Hoffmann
2014-03-10 12:49 ` Gerd Hoffmann [this message]
2014-03-10 12:49 ` [Qemu-devel] [PULL 8/9] ui/vnc: optimize setting in vnc_dpy_update() Gerd Hoffmann
2014-03-10 12:49 ` [Qemu-devel] [PULL 9/9] ui/vnc: disable adaptive update calculations if not needed Gerd Hoffmann
2014-03-11 11:37 ` [Qemu-devel] [PULL 0/9] vnc patches Peter Maydell
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=1394455753-13783-8-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=aliguori@amazon.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).