From: Gerd Hoffmann <kraxel@redhat.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH 3/3] vnc: throttle screen updates.
Date: Wed, 18 Mar 2009 17:09:16 +0100 [thread overview]
Message-ID: <49C11CAC.3060405@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 229 bytes --]
Hi,
This patch makes the vnc server code skip screen refreshes in case
there is data in the output buffer. This reduces the refresh rate to
throttle the bandwidth needed in case the network link is saturated.
cheers,
Gerd
[-- Attachment #2: 0003-vnc-throttle-screen-updates.patch --]
[-- Type: text/plain, Size: 2592 bytes --]
>From e1a20de776afe0d108fa94b2170f6d5690f9a24c Mon Sep 17 00:00:00 2001
From: Gerd Hoffmann <kraxel@redhat.com>
Date: Mon, 16 Mar 2009 21:37:48 +0100
Subject: [PATCH 3/3] vnc: throttle screen updates.
This patch makes the vnc server code skip screen refreshes in case
there is data in the output buffer. This reduces the refresh rate to
throttle the bandwidth needed in case the network link is saturated.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
vnc.c | 11 ++++++++++-
vnc.h | 1 +
2 files changed, 11 insertions(+), 1 deletions(-)
diff --git a/vnc.c b/vnc.c
index 0daaeac..8c60547 100644
--- a/vnc.c
+++ b/vnc.c
@@ -649,6 +649,7 @@ static void send_framebuffer_update(VncState *vs, int x, int y, int w, int h)
static void vnc_copy(VncState *vs, int src_x, int src_y, int dst_x, int dst_y, int w, int h)
{
+ vs->force_update = 1;
vnc_update_client(vs);
vnc_write_u8(vs, 0); /* msg id */
@@ -704,6 +705,12 @@ static void vnc_update_client(void *opaque)
vga_hw_update();
+ if (vs->output.offset && !vs->audio_cap && !vs->force_update) {
+ /* kernel send buffers are full -> drop frames to throttle */
+ qemu_mod_timer(vs->timer, qemu_get_clock(rt_clock) + VNC_REFRESH_INTERVAL);
+ return;
+ }
+
/*
* Walk through the guest dirty map.
* Check and copy modified bits from guest to server surface.
@@ -737,7 +744,7 @@ static void vnc_update_client(void *opaque)
server_row += ds_get_linesize(vs->ds);
}
- if (!has_dirty && !vs->audio_cap) {
+ if (!has_dirty && !vs->audio_cap && !vs->force_update) {
qemu_mod_timer(vs->timer, qemu_get_clock(rt_clock) + VNC_REFRESH_INTERVAL);
return;
}
@@ -781,6 +788,7 @@ static void vnc_update_client(void *opaque)
vs->output.buffer[saved_offset] = (n_rectangles >> 8) & 0xFF;
vs->output.buffer[saved_offset + 1] = n_rectangles & 0xFF;
vnc_flush(vs);
+ vs->force_update = 0;
}
@@ -1398,6 +1406,7 @@ static void framebuffer_update_request(VncState *vs, int incremental,
int i;
vs->need_update = 1;
+ vs->force_update = 1;
if (!incremental) {
for (i = 0; i < h; i++) {
vnc_set_bits(vs->guest.dirty[y_position + i],
diff --git a/vnc.h b/vnc.h
index c00fb00..0a2c66c 100644
--- a/vnc.h
+++ b/vnc.h
@@ -121,6 +121,7 @@ struct VncState
VncDisplay *vd;
int need_update;
+ int force_update;
uint32_t features;
int absolute;
int last_x;
--
1.6.1.3
next reply other threads:[~2009-03-18 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 16:09 Gerd Hoffmann [this message]
2009-03-19 17:25 ` [Qemu-devel] [PATCH 3/3] vnc: throttle screen updates Stefano Stabellini
2009-03-20 8:37 ` Gerd Hoffmann
2009-03-20 10:14 ` Stefano Stabellini
-- strict thread matches above, loose matches on Subject: below --
2009-03-20 11:31 [Qemu-devel] [PATCH 0/3] vnc patches Gerd Hoffmann
2009-03-20 11:31 ` [Qemu-devel] [PATCH 3/3] vnc: throttle screen updates Gerd Hoffmann
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=49C11CAC.3060405@redhat.com \
--to=kraxel@redhat.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 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.