From: Peter Lieven <pl@kamp.de>
To: qemu-devel@nongnu.org
Cc: corentincj@iksaif.net, Peter Lieven <pl@kamp.de>,
hengqing.hu@gmail.com, anthony@codemonkey.ws
Subject: [Qemu-devel] [PATCHv2 2/6] ui/vnc: derive cmp_bytes from VNC_DIRTY_PIXELS_PER_BIT
Date: Thu, 21 Nov 2013 09:51:13 +0100 [thread overview]
Message-ID: <1385023877-26524-3-git-send-email-pl@kamp.de> (raw)
In-Reply-To: <1385023877-26524-1-git-send-email-pl@kamp.de>
this allows for setting VNC_DIRTY_PIXELS_PER_BIT to different
values than 16 if desired.
Signed-off-by: Peter Lieven <pl@kamp.de>
---
ui/vnc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ui/vnc.c b/ui/vnc.c
index 67b1f75..0c93058 100644
--- a/ui/vnc.c
+++ b/ui/vnc.c
@@ -2695,7 +2695,7 @@ static int vnc_refresh_server_surface(VncDisplay *vd)
* Check and copy modified bits from guest to server surface.
* Update server dirty map.
*/
- cmp_bytes = 64;
+ cmp_bytes = VNC_DIRTY_PIXELS_PER_BIT * VNC_SERVER_FB_BYTES;
if (cmp_bytes > vnc_server_fb_stride(vd)) {
cmp_bytes = vnc_server_fb_stride(vd);
}
--
1.7.9.5
next prev parent reply other threads:[~2013-11-21 8:51 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 ` Peter Lieven [this message]
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
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=1385023877-26524-3-git-send-email-pl@kamp.de \
--to=pl@kamp.de \
--cc=anthony@codemonkey.ws \
--cc=corentincj@iksaif.net \
--cc=hengqing.hu@gmail.com \
--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).