From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3 of 4] [UPDATE ]single vnc server surface
Date: Fri, 31 Jul 2009 10:04:11 +0200 [thread overview]
Message-ID: <4A72A57B.7020203@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0907301353090.13932@kaball-desktop>
On 07/30/09 15:18, Stefano Stabellini wrote:
> This patch removes the server surface from VncState and adds a single
> server surface to VncDisplay for all the possible clients connected.
> Each client maintains a different dirty bitmap in VncState.
> The guest surface is moved to VncDisplay as well because we don't need
> to track guest updates in more than one place.
>
> This patch has been updated to handle copyrect correctly.
Well. Sort of. At least it has no screen corruption. The patch kills
a number of bandwith saving optimizations though.
Number one (the big one): vnc clients without copyrect support get a
*huge* penalty. Each vnc_copy call now sends a screen refresh to *all*
clients, not only the ones with copyrect support. And they get the
*whole* destination rectangle, not only the screen areas which did
actually change. Given that vnc_copy can happen much more frequently
than the refresh interval I think this increases the bandwith used *alot*.
Number two: In case we skip frames because we have data buffered (i.e.
kernel output pipe is full) we might send more updates than we have to.
With your patch the dirty bits of all screen updates are combined
together, including the screen updates skipped. So screen areas which
changed in the skipped frame, then changed back for the frame we
actually sent are updated nevertheless. This isn't the case without the
patch.
cheers,
Gerd
next prev parent reply other threads:[~2009-07-31 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 13:18 [Qemu-devel] [PATCH 3 of 4] [UPDATE ]single vnc server surface Stefano Stabellini
2009-07-31 8:04 ` Gerd Hoffmann [this message]
2009-07-31 16:51 ` Stefano Stabellini
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=4A72A57B.7020203@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.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.