From: Julian Seward <jseward@acm.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Reducing X communication bandwidth, take 2
Date: Wed, 14 Mar 2007 10:53:59 +0000 [thread overview]
Message-ID: <200703141053.59523.jseward@acm.org> (raw)
In-Reply-To: <200703140457.51798.mark.williamson@cl.cam.ac.uk>
On Wednesday 14 March 2007 04:57, Mark Williamson wrote:
> > > Here is a somewhat revised version of a patch I first made nearly
> > > three years ago. The original thread is
> >
> > The idea here is quite similar to what the VNC server does now.
> >
> > If this is desirable for SDL too, then perhaps we should find a way to
> > fold this into common code?
> >
> > Although, is there a compelling reason to use SDL over X instead of VNC?
>
> I sometimes do this sort of thing because it Just Works with no manual
> configuring of port forwarding etc. I don't necessarily like to do it for
> extended usage but it is very convenient.
Yes. VNC is all very nice (I use it a lot) but is hassle to set up,
what with making holes in firewalls and/or port forwarding etc. This
patch has the "it just works" property.
In fact I obtained (by far) the best remote X performance by using both
this patch and making the remote X connection with
"ssh -XC -o CompressionLevel=1". The patch knocks out the majority of
the data, and the ssh compression squashed what remained by more than a
factor of 10. Doing this it was hard to tell that QEMU was not running
locally.
J
next prev parent reply other threads:[~2007-03-14 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 1:52 [Qemu-devel] [PATCH] Reducing X communication bandwidth, take 2 Julian Seward
2007-03-14 3:39 ` Anthony Liguori
2007-03-14 4:57 ` Mark Williamson
2007-03-14 10:53 ` Julian Seward [this message]
2007-03-14 12:29 ` Johannes Schindelin
2007-03-16 18:40 ` Anthony Liguori
2007-03-16 20:53 ` Julian Seward
2007-03-16 21:09 ` Anthony Liguori
2007-03-16 21:38 ` Paul Brook
2007-03-19 16:07 ` [Qemu-devel] " Brian Johnson
2007-03-25 17:22 ` Anthony Liguori
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=200703141053.59523.jseward@acm.org \
--to=jseward@acm.org \
--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).