All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] starting qemu vnc session on a pre-allocated port
Date: Sun, 24 Jun 2007 17:40:22 -0500	[thread overview]
Message-ID: <467EF2D6.90501@codemonkey.ws> (raw)
In-Reply-To: <467EE5E0.5010605@codefidence.com>

Shahar Livne wrote:
> Hi Anthony,
>
> Thanks for your comment.
>
> 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.

Regards,

Anthony Liguori

> Regards,
> Shahar
>
>
>

  reply	other threads:[~2007-06-24 22:40 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 [this message]
2007-06-25  8:28       ` Gilad Ben-Yossef
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=467EF2D6.90501@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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.