qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Chris Frey <cdfrey@foursquare.net>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: text updates slow after commit 7d957bd8cbcbf56f7916d375e65042d767f544b5
Date: Tue, 28 Apr 2009 17:12:00 -0500	[thread overview]
Message-ID: <49F77F30.2000703@codemonkey.ws> (raw)
In-Reply-To: <20090428220018.GA30256@foursquare.net>

Chris Frey wrote:
> On Tue, Apr 28, 2009 at 04:40:58PM -0500, Anthony Liguori wrote:
>   
>> What's your configuration (host type, etc.)?  Are you remoting over X?
>>     
>
> Oops, forgot to say that I am using X through an SSH forward.
>
> 	ssh -Y -a -2 ...
>   

That's what I figured.  You should use -vnc instead.

In the 0.10.x series, we changed the way we interact with libsdl.  We're 
now relying on libsdl to do pixel conversion.  It appears that SDL is 
sending a lot more data to the X server when you do this than it was 
previously.  The result is a marked slowdown when remoting QEMU over X.

Fortunately, we have an integrated remoting mechanism (-vnc) that 
doesn't suffer from these problems.

If you think this really should be addressed, I'd suggest reporting it 
to the SDL community as they're the ones who are best positioned to 
detect that it's a remote X server and then do local conversion 
appropriately.  Alternatively, I suspect using an X protocol optimizer 
(like NX) would make this problem go away.

Regards,

Anthony Liguori

> - Chris
>
>   

      reply	other threads:[~2009-04-28 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 21:25 [Qemu-devel] text updates slow after commit 7d957bd8cbcbf56f7916d375e65042d767f544b5 Chris Frey
2009-04-28 21:40 ` Anthony Liguori
2009-04-28 21:55   ` [Qemu-devel] " Chris Frey
2009-04-28 22:00   ` Chris Frey
2009-04-28 22:12     ` Anthony Liguori [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=49F77F30.2000703@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=cdfrey@foursquare.net \
    --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).