From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: James Harper <james.harper@bendigoit.com.au>
Cc: xen-devel@lists.xensource.com
Subject: Re: Qemu vnc color depth
Date: Mon, 11 Feb 2008 11:37:40 +0000 [thread overview]
Message-ID: <47B03384.6030109@eu.citrix.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D0131ABB3@trantor>
James Harper wrote:
>> The basic idea is that the vnc client is the one that should do the
>> colour conversion, if necessary.
>
> What impact, if any, does this have on the bandwidth required for the
> VNC connection? I've been using VNC to access HVM Xen clients over a
> 512k link lately and it's only barely acceptable. My color level is set
> to 'Low (64 Colors)'. If the client is doing the conversion then doesn't
> this mean that the server has to transmit 16/24/32 bits of color
> information to the client, rather than 6?
>
> Or more likely, maybe I don't understand the implications of your patch
> :)
>
It is the opposite :)
Now most vnc clients run on 32 bpp display, so they automatically ask
for 32 bpp connections to the server, even if the guest is using 16 bpp.
This is a waste of bandwidth.
Using my patch together with the right configuration of your vnc client
you can just use the bandwidth needed to preserve the colour depth
resolution of the guest and nothing more.
next prev parent reply other threads:[~2008-02-11 11:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 11:20 Qemu vnc color depth Stefano Stabellini
2008-02-11 11:31 ` James Harper
2008-02-11 11:37 ` Stefano Stabellini [this message]
2008-02-11 14:54 ` Daniel P. Berrange
2008-02-11 15:18 ` Stefano Stabellini
2008-02-11 15:29 ` Daniel P. Berrange
2008-02-11 15:47 ` Anthony Liguori
2008-02-12 11:23 ` Stefano Stabellini
2008-02-12 14:56 ` Anthony Liguori
2008-02-12 15:10 ` Stefano Stabellini
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=47B03384.6030109@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.com \
/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.