All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Peter Lieven <pl@kamp.de>, qemu-devel@nongnu.org
Cc: corentincj@iksaif.net, hengqing.hu@gmail.com, anthony@codemonkey.ws
Subject: Re: [Qemu-devel] RESEND: [PATCHv2 0/6] ui/vnc: update optimizations
Date: Wed, 04 Dec 2013 19:20:41 +0100	[thread overview]
Message-ID: <529F7279.70808@weilnetz.de> (raw)
In-Reply-To: <529F6CD6.30005@kamp.de>

Am 04.12.2013 18:56, schrieb Peter Lieven:
> Ping
>
> Am 21.11.2013 09:51, schrieb Peter Lieven:
>> this series includes several optimizations for the ui/vnc guest to server and server to client
>> update cycles. comments/reviews appreciated.
>>
>> v1->v2: - new patches 2,4,5
>>         - patch3: added performance test [Anthony]
>>         - patch3: further optimized the vnc_update_client by searching for the next zero bit
>>           with find_next_zero_bit.
>>         - patch3: further optimized vnc_dpy_switch by using bitmap_set to mask bits dirty.
>>
>> Peter
>>
>> Peter Lieven (6):
>>   ui/vnc: introduce VNC_DIRTY_PIXELS_PER_BIT macro
>>   ui/vnc: derive cmp_bytes from VNC_DIRTY_PIXELS_PER_BIT
>>   ui/vnc: optimize dirty bitmap tracking
>>   ui/vnc: optimize clearing in find_and_clear_dirty_height()
>>   ui/vnc: optimize setting in vnc_dpy_update()
>>   ui/vnc: disable adaptive update calculations if not needed
>>
>>  ui/vnc.c |  185 ++++++++++++++++++++++++++++++++++++--------------------------
>>  ui/vnc.h |    9 ++-
>>  2 files changed, 115 insertions(+), 79 deletions(-)

Hallo Peter,

there was an e-mail from Eric which you might consider in a 2nd version
of your patch series.

Please check also your patches using scripts/checkpatch.pl. Some of them
currently produce warnings:

total: 0 errors, 1 warnings, 139 lines
checked0001-ui-vnc-introduce-VNC_DIRTY_PIXELS_PER_BIT-macro.patch

total: 0 errors, 6 warnings, 212 lines
checked0003-ui-vnc-optimize-dirty-bitmap-tracking.patch

total: 0 errors, 1 warnings, 17 lines
checked0005-ui-vnc-optimize-setting-in-vnc_dpy_update.patch

I think it would also be reasonable to fix the coding style for this
code location in a separate patch
before modifying the else statement, but maybe this is optional:

     else
-        w_lim = w - (w_lim % 16);
+        w_lim = w - (w_lim % VNC_DIRTY_PIXELS_PER_BIT);


Viele Grüße

Stefan Weil

  reply	other threads:[~2013-12-04 18:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21  8:51 [Qemu-devel] [PATCHv2 0/6] ui/vnc: update optimizations Peter Lieven
2013-11-21  8:51 ` [Qemu-devel] [PATCHv2 1/6] ui/vnc: introduce VNC_DIRTY_PIXELS_PER_BIT macro Peter Lieven
2013-11-21  8:51 ` [Qemu-devel] [PATCHv2 2/6] ui/vnc: derive cmp_bytes from VNC_DIRTY_PIXELS_PER_BIT Peter Lieven
2013-11-21  8:51 ` [Qemu-devel] [PATCHv2 3/6] ui/vnc: optimize dirty bitmap tracking Peter Lieven
2013-11-21 15:16   ` Eric Blake
2013-11-21  8:51 ` [Qemu-devel] [PATCHv2 4/6] ui/vnc: optimize clearing in find_and_clear_dirty_height() Peter Lieven
2013-11-21  8:51 ` [Qemu-devel] [PATCHv2 5/6] ui/vnc: optimize setting in vnc_dpy_update() Peter Lieven
2013-11-21  8:51 ` [Qemu-devel] [PATCHv2 6/6] ui/vnc: disable adaptive update calculations if not needed Peter Lieven
2013-12-04 17:56 ` [Qemu-devel] RESEND: [PATCHv2 0/6] ui/vnc: update optimizations Peter Lieven
2013-12-04 18:20   ` Stefan Weil [this message]
2013-12-04 21:04     ` 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=529F7279.70808@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=anthony@codemonkey.ws \
    --cc=corentincj@iksaif.net \
    --cc=hengqing.hu@gmail.com \
    --cc=pl@kamp.de \
    --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.