All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@kamp.de>
To: qemu-devel@nongnu.org
Cc: sw@weilnetz.de, Peter Lieven <pl@kamp.de>,
	xiawenc@linux.vnet.ibm.com, aliguori@amazon.com
Subject: [Qemu-devel] [PATCHv4 4/6] ui/vnc: optimize clearing in find_and_clear_dirty_height()
Date: Wed,  8 Jan 2014 10:08:36 +0100	[thread overview]
Message-ID: <1389172118-25402-5-git-send-email-pl@kamp.de> (raw)
In-Reply-To: <1389172118-25402-1-git-send-email-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>
---
 ui/vnc.c |    5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/ui/vnc.c b/ui/vnc.c
index 3412cdf..4117230 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.7.9.5

  parent reply	other threads:[~2014-01-08  9:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08  9:08 [Qemu-devel] [PATCHv4 0/6] ui/vnc: update optimizations Peter Lieven
2014-01-08  9:08 ` [Qemu-devel] [PATCHv4 1/6] ui/vnc: introduce VNC_DIRTY_PIXELS_PER_BIT macro Peter Lieven
2014-01-09  4:44   ` Wenchao Xia
2014-01-08  9:08 ` [Qemu-devel] [PATCHv4 2/6] ui/vnc: derive cmp_bytes from VNC_DIRTY_PIXELS_PER_BIT Peter Lieven
2014-01-08  9:08 ` [Qemu-devel] [PATCHv4 3/6] ui/vnc: optimize dirty bitmap tracking Peter Lieven
2014-01-09  7:37   ` Wenchao Xia
2014-01-08  9:08 ` Peter Lieven [this message]
2014-01-09  7:58   ` [Qemu-devel] [PATCHv4 4/6] ui/vnc: optimize clearing in find_and_clear_dirty_height() Wenchao Xia
2014-01-08  9:08 ` [Qemu-devel] [PATCHv4 5/6] ui/vnc: optimize setting in vnc_dpy_update() Peter Lieven
2014-01-09  8:16   ` Wenchao Xia
2014-01-08  9:08 ` [Qemu-devel] [PATCHv4 6/6] ui/vnc: disable adaptive update calculations if not needed Peter Lieven
2014-01-09  8:29   ` Wenchao Xia
2014-01-09 16:25     ` Peter Lieven
2014-01-10  3:09       ` Wenchao Xia
2014-01-10 22:28         ` Peter Lieven
2014-01-13  2:42           ` Wenchao Xia
2014-01-13  8:27             ` Peter Lieven
2014-01-20  9:54 ` [Qemu-devel] [PATCHv4 0/6] ui/vnc: update optimizations Peter Lieven
2014-02-03  9:28 ` 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=1389172118-25402-5-git-send-email-pl@kamp.de \
    --to=pl@kamp.de \
    --cc=aliguori@amazon.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    --cc=xiawenc@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.