[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC v5 17/26] qmp: add new event "request-dropped"
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] [RFC v5 17/26] qmp: add new event "request-dropped" |
Date: |
Thu, 14 Dec 2017 11:32:09 +0000 |
User-agent: |
Mutt/1.9.1 (2017-09-22) |
On Tue, Dec 05, 2017 at 01:51:51PM +0800, Peter Xu wrote:
> +##
> +# @RequestDropReason:
> +#
> +# Reasons that caused one command to be dropped.
> +#
> +# @queue-full: the queue of request is full.
Please add:
This can only occur when the client sends a new non-oob command before
the response to the previous non-oob command has been received.
This way simple clients that only send 1 command at a time don't need to
worry about queue-full. I think this documents the behavior implemented
by this patch series.
signature.asc
Description: PGP signature
- Re: [Qemu-devel] [RFC v5 15/26] monitor: let suspend_cnt be thread safe, (continued)
[Qemu-devel] [RFC v5 17/26] qmp: add new event "request-dropped", Peter Xu, 2017/12/05
[Qemu-devel] [RFC v5 18/26] monitor: send event when request queue full, Peter Xu, 2017/12/05
[Qemu-devel] [RFC v5 19/26] qapi: introduce new cmd option "allow-oob", Peter Xu, 2017/12/05
[Qemu-devel] [RFC v5 20/26] qmp: support out-of-band (oob) execution, Peter Xu, 2017/12/05