From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: sw@weilnetz.de, aliguori@amazon.com
Subject: Re: [Qemu-devel] [PATCHv4 6/6] ui/vnc: disable adaptive update calculations if not needed
Date: Fri, 10 Jan 2014 11:09:44 +0800 [thread overview]
Message-ID: <52CF6478.2030207@linux.vnet.ibm.com> (raw)
In-Reply-To: <52CECD82.4030809@kamp.de>
于 2014/1/10 0:25, Peter Lieven 写道:
> Am 09.01.2014 09:29, schrieb Wenchao Xia:
>> 于 2014/1/8 17:08, Peter Lieven 写道:
>>> Signed-off-by: Peter Lieven <pl@kamp.de>
>>> ---
>>> ui/vnc.c | 9 +++++++++
>>> 1 file changed, 9 insertions(+)
>>>
>>> diff --git a/ui/vnc.c b/ui/vnc.c
>>> index da552fe..a742d32 100644
>>> --- a/ui/vnc.c
>>> +++ b/ui/vnc.c
>>> @@ -3170,7 +3170,9 @@ void vnc_display_open(DisplayState *ds, const char *display, Error **errp)
>>> acl = 1;
>>> #endif
>>> } else if (strncmp(options, "lossy", 5) == 0) {
>>> +#ifdef CONFIG_VNC_JPEG
>>> vs->lossy = true;
>>> +#endif
>>> } else if (strncmp(options, "non-adaptive", 12) == 0) {
>>> vs->non_adaptive = true;
>>> } else if (strncmp(options, "share=", 6) == 0) {
>>> @@ -3187,6 +3189,13 @@ void vnc_display_open(DisplayState *ds, const char *display, Error **errp)
>>> }
>>> }
>>>
>>> + /* adaptive updates are only used with tight encoding and
>>> + * if lossy updates are enabled so we can disable all the
>>> + * calculations otherwise */
>>> + if (!vs->lossy) {
>>> + vs->non_adaptive = true;
>>> + }
>>> +
>> The code seems: if vs->loosy == false, then vs->non_adaptive = true,
>> translate as: if loosy update is not used, then don't do adaptive
>> update., which doesn't conform with the comments. I am not sure if this
>> is on expectation.
> It don't see the logic break. The option means non_adaptive, not adaptive.
>
> I write "adaptive updates are only used ... with lossy updates...". Which
So tight encoding means loosy updates?
> is the same as "without lossy updates we don't need adaptive updates".
>
> Peter
>
>>
>>
>>> #ifdef CONFIG_VNC_TLS
>>> if (acl && x509 && vs->tls.x509verify) {
>>> if (!(vs->tls.acl = qemu_acl_init("vnc.x509dname"))) {
>>>
>
>
next prev parent reply other threads:[~2014-01-10 3:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 9:08 [Qemu-devel] [PATCHv4 0/6] ui/vnc: update optimizations Peter Lieven
2014-01-08 9:08 ` [Qemu-devel] [PATCHv4 1/6] ui/vnc: introduce VNC_DIRTY_PIXELS_PER_BIT macro Peter Lieven
2014-01-09 4:44 ` Wenchao Xia
2014-01-08 9:08 ` [Qemu-devel] [PATCHv4 2/6] ui/vnc: derive cmp_bytes from VNC_DIRTY_PIXELS_PER_BIT Peter Lieven
2014-01-08 9:08 ` [Qemu-devel] [PATCHv4 3/6] ui/vnc: optimize dirty bitmap tracking Peter Lieven
2014-01-09 7:37 ` Wenchao Xia
2014-01-08 9:08 ` [Qemu-devel] [PATCHv4 4/6] ui/vnc: optimize clearing in find_and_clear_dirty_height() Peter Lieven
2014-01-09 7:58 ` Wenchao Xia
2014-01-08 9:08 ` [Qemu-devel] [PATCHv4 5/6] ui/vnc: optimize setting in vnc_dpy_update() Peter Lieven
2014-01-09 8:16 ` Wenchao Xia
2014-01-08 9:08 ` [Qemu-devel] [PATCHv4 6/6] ui/vnc: disable adaptive update calculations if not needed Peter Lieven
2014-01-09 8:29 ` Wenchao Xia
2014-01-09 16:25 ` Peter Lieven
2014-01-10 3:09 ` Wenchao Xia [this message]
2014-01-10 22:28 ` Peter Lieven
2014-01-13 2:42 ` Wenchao Xia
2014-01-13 8:27 ` Peter Lieven
2014-01-20 9:54 ` [Qemu-devel] [PATCHv4 0/6] ui/vnc: update optimizations Peter Lieven
2014-02-03 9:28 ` Peter Lieven
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=52CF6478.2030207@linux.vnet.ibm.com \
--to=xiawenc@linux.vnet.ibm.com \
--cc=aliguori@amazon.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).