From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Glauber Costa <glommer@redhat.com>,
"aliguori@us.ibm.com" <aliguori@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Re: [PATCH] update server bits on vnc_update
Date: Tue, 21 Jul 2009 15:19:57 +0200 [thread overview]
Message-ID: <4A65C07D.6080103@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0907211344260.12499@kaball-desktop>
On 07/21/09 14:56, Stefano Stabellini wrote:
> we call vga_hw_update in vnc_update_client, that means we call it once
> per vnc client connected! We should call it only once, probably in a
> separate timer, that is enabled only if at least one client is connect.
Good point. Even better would be a timer shared by all clients, then
loop over all clients (pretty much like vnc_dpy_update calls vnc_update
for all connected clients). That would make moving vga_hw_update out of
the loop trivial ;)
> I also don't like the fact that we are allocating a server surface per
> client connected, this can become a problem very fast: I think we could
> probably get away with just one server surface for all the clients.
I don't think so. server surface matches the vnc clients view of the
framebuffer. We need that to avoid sending screen updates for regions
which didn't change. Different clients can have a different views here
for a number of reasons: Because they support different feature sets.
Because we try to skip frames if the pipe is full. Thus sharing the
server surface is non-trivial and we'll lose certain optimization when
doing that.
cheers,
Gerd
prev parent reply other threads:[~2009-07-21 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 4:47 [Qemu-devel] [PATCH] update server bits on vnc_update Glauber Costa
2009-07-18 16:20 ` [Qemu-devel] " Anthony Liguori
2009-07-19 7:57 ` [Qemu-devel] " Lucas Meneghel Rodrigues
2009-07-21 8:09 ` [Qemu-devel] " Gerd Hoffmann
2009-07-21 11:19 ` Gerd Hoffmann
2009-07-21 12:56 ` Stefano Stabellini
2009-07-21 13:16 ` Stefano Stabellini
2009-07-21 13:19 ` Gerd Hoffmann [this message]
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=4A65C07D.6080103@redhat.com \
--to=kraxel@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=glommer@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 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).