qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Threaded VNC server status - time to enable by default ?
Date: Wed, 20 Jun 2012 10:15:28 +0100	[thread overview]
Message-ID: <20120620091528.GI20792@redhat.com> (raw)

We recently had a request in Fedora to enable the VNC server thread
support in our builds of QEMU. There have been periodic messages on
this list that suggest the threaded VNC server has better performance
and less latency.

My view though, is that there must be some good reason why QEMU does
not enable it by default already. Can anyone say why QEMU has not
enabled the VNC server threads by default ?

If there is no such reason, can we just kill the configure options
--{disable,enable}-vnc-thread, and have everyone use the VNC server
thread support forever more. I struggle to see the point in maintaining
these two separate codepaths for the VNC server. Whichever one is
not the default is, IMHO, destined to bitrot through lack of widespread
testing and so we're better off getting everyone to use & test the
same codepath.

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

             reply	other threads:[~2012-06-20  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20  9:15 Daniel P. Berrange [this message]
2012-06-20 12:58 ` [Qemu-devel] Threaded VNC server status - time to enable by default ? Anthony Liguori
2012-06-20 13:03   ` Daniel P. Berrange

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=20120620091528.GI20792@redhat.com \
    --to=berrange@redhat.com \
    --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).