From: Julian Seward <jseward@acm.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Reducing X communication bandwidth
Date: Sun, 11 Jul 2004 12:22:02 +0100 [thread overview]
Message-ID: <200407111222.02531.jseward@acm.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0407111151100.14752@wgmdd8.biozentrum.uni-wuerzburg.de>
On Sunday 11 July 2004 10:53, Johannes Schindelin wrote:
> Hi,
>
> On Sat, 10 Jul 2004, Julian Seward wrote:
> > The attached patch against sdl.c fixes this. It keeps a shadow
> > copy of video memory. When a request arrives at sdl_update()
> > to redraw an area, the area is compared against the shadow copy,
> > and only the parts that have really changed are passed to
> > SDL_UpdateRect(). The comparison is done at a granularity of
> > 32x32 chunks of pixels.
>
> Why does this remind me of VNC? In fact, that kind of application is the
> exact reason I started my VNC patch. It could also be useful as a Windows
> 98 Terminal Server...
Exactly -- I got the idea from VNC. First I noticed that using qemu
just as a remote X client gave appalling performance *but* when you
run it on a remote VNC server and connect with vncviewer, the results
is quite usable. That immediately suggests that vnc found a lot of
redundant screen updates and did not bother to send them over the
network, and at that point I started hacking :-)
J
next prev parent reply other threads:[~2004-07-11 11:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 8:45 [Qemu-devel] Reducing X communication bandwidth Julian Seward
2004-07-10 9:10 ` Jan Dittmer
2004-07-11 10:15 ` Hetz Ben Hamo
2004-07-10 10:53 ` Jan Dittmer
2004-07-11 8:20 ` Jan Dittmer
2004-07-11 11:18 ` Julian Seward
2004-07-10 12:00 ` Brad Campbell
2004-07-10 12:42 ` Julian Seward
2004-07-10 13:53 ` Fabrice Bellard
2004-07-11 9:53 ` Johannes Schindelin
2004-07-11 11:22 ` Julian Seward [this message]
2004-07-12 10:16 ` Johannes Schindelin
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=200407111222.02531.jseward@acm.org \
--to=jseward@acm.org \
--cc=Johannes.Schindelin@gmx.de \
--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.