qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gilad Ben-Yossef <gilad@codefidence.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] starting qemu vnc session on a pre-allocated port
Date: Mon, 25 Jun 2007 11:28:54 +0300	[thread overview]
Message-ID: <467F7CC6.6000207@codefidence.com> (raw)
In-Reply-To: <467EF2D6.90501@codemonkey.ws>

Hi Anthony,

Thanks for the feedback.

I'm afraid I'm to blame for the idea to this patch (but Shahar was the one
that actually did the real work, I'm just bothering him).

Anthony Liguori wrote:

>>
>> The problem with the solution you suggest is that all VNC traffic will 
>> be first sent to the unix domain socket, and then copied to the TCP 
>> socket. This double work may be acceptable if we're talking about one 
>> instance of qemu, but as I said, I run many concurrent sessions which 
>> create too much load. In the solution I suggest, this extra copying is 
>> not needed.
> 
> 
> You're optimizing prematurely.  The overhead of the copy is negligible 
> for something like VNC.  Under normal circumstances, we're talking about 
> 30-100k/s.  During idle usage, the bandwidth drops to almost nothing.
> 

There are also the double context switches, more file descriptors and
extra proccess to handle the copy but you are abosutly right - we have
no indication what so ever that this really has any measurable impact
on perfomance.

I guess it's easier to resort to perfomance as an excuse since it involves
things you can measure (even if they are meaningless) rather then trying
to justify a design decision because it simply looks better. ;-)

I'll try to do just that, anyway:

Using Unix domain sockets would require adding extra code in some other proccess
that will handle the socket to socket transfer. About 15 lines of code that must
be running for as long as qemu does to handle the communication. That code still
needs to be mnaintained, seperate from qemu, by anyone that trying to do something
similar (so we have sync problems etc.)

On the other hand, the change to qemu is ~5 lines (option parsing not included ;-)
It's initaliation code only (no suprises mid run) and is maintained as part of qemu
with exact same functionality.

If you think users other then us will use the patch (and we believe they will),
we think it'll be useful for this to be included in qemu mainline.

Anyway, thanks for reading this long email and for qemu VNC support in general :-)

Cheers,
Gilad

-- 
Gilad Ben-Yossef <gilad@codefidence.com>
Codefidence. A name you can trust(tm)
http://www.codefidence.com
Phone: +972.3.7515563 ext. 201  | Cellular: +972.52.8260388
SIP: gilad@pbx.codefidence.com	| Fax: +972.3.7515503

	Lacking fins or tail
	the gefilte fish swims with
	great difficulty.

	  -- A Jewish Haiku

  reply	other threads:[~2007-06-25  8:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-24 13:05 [Qemu-devel] [PATCH] starting qemu vnc session on a pre-allocated port Shahar Livne
2007-06-24 14:07 ` Anthony Liguori
2007-06-24 21:45   ` Shahar Livne
2007-06-24 22:40     ` Anthony Liguori
2007-06-25  8:28       ` Gilad Ben-Yossef [this message]
2007-06-25 11:55         ` Anthony Liguori
2007-06-26 10:17           ` Gilad Ben-Yossef
2007-06-26 10:48             ` Jannes Faber
2007-06-28 15:25             ` Anthony Liguori
2007-06-30 21:15               ` Gilad Ben-Yossef
2007-07-01 15:33                 ` Anthony Liguori
2007-06-24 19:16 ` Paul Brook
2007-06-24 20:12   ` Anthony Liguori
  -- strict thread matches above, loose matches on Subject: below --
2007-06-25 14:58 n schembr

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=467F7CC6.6000207@codefidence.com \
    --to=gilad@codefidence.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).