qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Threaded VNC server status - time to enable by default ?
Date: Wed, 20 Jun 2012 07:58:53 -0500	[thread overview]
Message-ID: <4FE1C90D.7090908@codemonkey.ws> (raw)
In-Reply-To: <20120620091528.GI20792@redhat.com>

On 06/20/2012 04:15 AM, Daniel P. Berrange wrote:
> 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.

At the time it was introduced, QEMU still has no hard requirement on having 
pthreads as a dependency (the I/O thread was still optional).

We're past that point now so there's no harm in unconditionally enabling the VNC 
thread pool.

Regards,

Anthony Liguori

>
> Regards,
> Daniel

  reply	other threads:[~2012-06-20 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20  9:15 [Qemu-devel] Threaded VNC server status - time to enable by default ? Daniel P. Berrange
2012-06-20 12:58 ` Anthony Liguori [this message]
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=4FE1C90D.7090908@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=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).