All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: amit.shah@redhat.com, marcandre.lureau@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/7] monitor: Simplify event throttling
Date: Thu, 15 Oct 2015 16:43:13 -0600	[thread overview]
Message-ID: <56202C01.2020704@redhat.com> (raw)
In-Reply-To: <1444921716-9511-3-git-send-email-armbru@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]

On 10/15/2015 09:08 AM, Markus Armbruster wrote:
> The event throttling state machine is hard to understand.  I'm not
> sure it's entirely correct.  Rewrite it in a more straightforward
> manner:
> 
> State 1: No event sent recently (less than evconf->rate ns ago)
> 
>     Invariant: evstate->timer is not pending, evstate->qdict is null
> 
>     On event: send event, arm timer, goto state 2
> 
> State 2: Event sent recently, no additional event being delayed
> 
>     Invariant: evstate->timer is pending, evstate->qdict is null
> 
>     On event: store it in evstate->qdict, goto state 3
> 
>     On timer: goto state 1
> 
> State 3: Event sent recently, additional event being delayed
> 
>     Invariant: evstate->timer is pending, evstate->qdict is non-null
> 
>     On event: store it in evstate->qdict, goto state 3
> 
>     On timer: send evstate->qdict, clear evstate->qdict,
>               arm timer, goto state 2
> 
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
>  monitor.c    | 63 +++++++++++++++++++++++++++++-------------------------------
>  trace-events |  4 ++--
>  2 files changed, 32 insertions(+), 35 deletions(-)
> 

Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2015-10-15 22:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 15:08 [Qemu-devel] [PATCH 0/7] Throttle event VSERPORT_CHANGE separately by "id" Markus Armbruster
2015-10-15 15:08 ` [Qemu-devel] [PATCH 1/7] monitor: Reduce casting of QAPI event QDict Markus Armbruster
2015-10-15 15:08 ` [Qemu-devel] [PATCH 2/7] monitor: Simplify event throttling Markus Armbruster
2015-10-15 22:43   ` Eric Blake [this message]
2015-10-15 15:08 ` [Qemu-devel] [PATCH 3/7] monitor: Switch from timer_new() to timer_new_ns() Markus Armbruster
2015-10-15 22:44   ` Eric Blake
2015-10-15 15:08 ` [Qemu-devel] [PATCH 4/7] monitor: Split MonitorQAPIEventConf off MonitorQAPIEventState Markus Armbruster
2015-10-15 15:08 ` [Qemu-devel] [PATCH 5/7] monitor: Turn monitor_qapi_event_state[] into a hash table Markus Armbruster
2015-10-15 15:08 ` [Qemu-devel] [PATCH 6/7] monitor: Throttle event VSERPORT_CHANGE separately by "id" Markus Armbruster
2015-10-15 15:08 ` [Qemu-devel] [PATCH 7/7] docs: Document QMP event rate limiting Markus Armbruster
2015-10-15 22:46   ` Eric Blake
2015-10-15 15:30 ` [Qemu-devel] [PATCH 0/7] Throttle event VSERPORT_CHANGE separately by "id" Markus Armbruster
2015-10-27 14:51 ` [Qemu-devel] [PATCH 4.5/7] glib: add compatibility interface for g_hash_table_add() Markus Armbruster
2015-10-27 15:10   ` Eric Blake
2015-10-27 16:06     ` Markus Armbruster

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=56202C01.2020704@redhat.com \
    --to=eblake@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --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.