From: Brad Campbell <brad@wasp.net.au>
To: jseward@acm.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Reducing X communication bandwidth
Date: Sat, 10 Jul 2004 16:00:02 +0400 [thread overview]
Message-ID: <40EFDA42.2070704@wasp.net.au> (raw)
In-Reply-To: <200407100945.06998.jseward@acm.org>
Julian Seward wrote:
> QEMU is great, but one specific problem has made it unusable
> for me so far. The (fast) machine I want to run QEMU on is not
> the same as my (slow) machine which is on my desk. That is,
> I want to do the usual X "export DISPLAY=someothermachine:0.0"
> game.
>
> These machines are connected by an old-fashioned 10 Mbit/sec
> network, which you may argue is obsolete, but I would argue
> represents reasonably the approximate bandwidth of 802.11b/g
> LANs which are common now.
>
> Anyway, QEMU from cvs is unusable like this, at least when
> running WinXP or Win2K. The SDL layer (qemu/sdl.c) blasts
> huge numbers of pixels across the network in response to even
> the simplest graphical operations. Notably, moving the mouse
> pointer is appalling, with an update rate of about twice per
> second, which is hopeless.
>
Great patch! This patch combined with ssh -X -C makes qemu usable over my wireless link between
office and home. Still a little laggy but at least usable.
Cheers!
Brad
next prev parent reply other threads:[~2004-07-10 12:02 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 [this message]
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
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=40EFDA42.2070704@wasp.net.au \
--to=brad@wasp.net.au \
--cc=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 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.