qemu-devel.nongnu.org archive mirror
 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 0/6] ui/vnc: update optimizations
Date: Wed,  8 Jan 2014 10:08:32 +0100	[thread overview]
Message-ID: <1389172118-25402-1-git-send-email-pl@kamp.de> (raw)

this series includes several optimizations for the ui/vnc guest to server and server to client
update cycles. comments/reviews appreciated.

v3->v4: - patch 1,4,6 unchanged
        - patch 2: fix 2 missing changes from 16 -> VNC_DIRTY_PIXELS_PER_BIT [Wenchao]
        - patch 3: fixed missing roundup of width in vnc_dpy_switch [Wenchao]
        - patch 3: fixed x offset calculation in vnc_refresh_server_surface
        - patch 5: fixed missing roundup of width in vnc_dpy_update, cleaned up function
v2->v3: - fixed checkpatch warnings [Stefan]
        - fixed an old coding style violation [Stefan]
v1->v2: - new patches 2,4,5
        - patch3: added performance test [Anthony]
        - patch3: further optimized the vnc_update_client by searching for the next zero bit
          with find_next_zero_bit.
        - patch3: further optimized vnc_dpy_switch by using bitmap_set to mask bits dirty.

Peter Lieven (6):
  ui/vnc: introduce VNC_DIRTY_PIXELS_PER_BIT macro
  ui/vnc: derive cmp_bytes from VNC_DIRTY_PIXELS_PER_BIT
  ui/vnc: optimize dirty bitmap tracking
  ui/vnc: optimize clearing in find_and_clear_dirty_height()
  ui/vnc: optimize setting in vnc_dpy_update()
  ui/vnc: disable adaptive update calculations if not needed

 ui/vnc.c |  206 +++++++++++++++++++++++++++++++++++---------------------------
 ui/vnc.h |   10 ++-
 2 files changed, 127 insertions(+), 89 deletions(-)

-- 
1.7.9.5

             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 Peter Lieven [this message]
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 ` [Qemu-devel] [PATCHv4 4/6] ui/vnc: optimize clearing in find_and_clear_dirty_height() Peter Lieven
2014-01-09  7:58   ` 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-1-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 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).