From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0 of 3] vnc and vga improvements
Date: Sat, 06 Sep 2008 21:51:54 -0500 [thread overview]
Message-ID: <48C341CA.30002@codemonkey.ws> (raw)
In-Reply-To: <48B7C6A7.2050706@redhat.com>
Gerd Hoffmann wrote:
> Anthony Liguori wrote:
>
>> Stefano Stabellini wrote:
>>
>> I have mixed feelings about this. On the one hand, reducing the copying
>> is a good thing. On the other hand, we pretty much make it impossible
>> to ever support multiple clients.
>>
>
> Getting rid of the color space conversions is a good thing, even in case
> we can't drop the separate buffers and the memcpys. Right now the vnc
> server runs at 32bit unconditionally. Having it run at 16bpp in case
> the guest uses 16bpp is still a win because we (a) have to handle less
> memory and (b) can to a straight copy instead of a pixel conversion.
>
It's not as big of a win as it seems as there is only one client that
can handle this ATM :-)
> And maybe the buffer sharing can be implemented in a way that we can
> turn it on and off at runtime? So the common case of at most one client
> can run with buffer sharing, otherwise we copy to per-client buffers?
>
Yes, I would like this. I haven't yet looked closely at the patches,
but if this is the case, I would be inclined to apply them.
Regards,
Anthony Liguori
> I'm not a vnc protocol expert though.
>
> Looking at the patches, it seems buffer sharing is optional already
> (usage depending on the color depth right now it seems).
>
> cheers,
> Gerd
>
>
>
>
>
prev parent reply other threads:[~2008-09-07 2:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 15:49 [Qemu-devel] [PATCH 0 of 3] vnc and vga improvements Stefano Stabellini
2008-08-28 20:07 ` Anthony Liguori
2008-08-29 9:51 ` Stefano Stabellini
2008-08-29 9:51 ` Gerd Hoffmann
2008-08-29 10:02 ` Samuel Thibault
2008-08-29 10:12 ` Stefano Stabellini
2008-09-07 2:51 ` Anthony Liguori [this message]
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=48C341CA.30002@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 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).