From: Andrey Shinkevich via <qemu-devel@nongnu.org>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, mreitz@redhat.com,
mdroth@linux.vnet.ibm.com, thuth@redhat.com, lvivier@redhat.com,
armbru@redhat.com, dgilbert@redhat.com, pbonzini@redhat.com,
den@openvz.org, vsementsov@virtuozzo.com,
andrey.shinkevich@virtuozzo.com
Subject: [PATCH v3 0/5] Increase amount of data for monitor to read
Date: Fri, 27 Nov 2020 16:35:41 +0300 [thread overview]
Message-ID: <1606484146-913540-1-git-send-email-andrey.shinkevich@virtuozzo.com> (raw)
The subject was discussed here:
https://lists.gnu.org/archive/html/qemu-devel/2017-05/msg00206.html
https://patchew.org/QEMU/20190610105906.28524-1-dplotnikov@virtuozzo.com/#
Message-ID: <31dd78ba-bd64-2ed6-3c8f-eed4e904d14c@virtuozzo.com>
and v2:
Message-Id: <1606146274-246154-1-git-send-email-andrey.shinkevich@virtuozzo.com>
This series is a solution for the issue with overflow of the monitor queue
with QMP requests if we keep the maximum queue length unchanged (=8).
v3:
01: New
02: New
03: The additional little JSON parser removed and the resources of the
existing JSON parser were used to track the end of a QMP command.
04: The amount of read input data increases only.
Andrey Shinkevich (4):
monitor: change function obsolete name in comments
monitor: drain requests queue with 'channel closed' event
monitor: let QMP monitor track JSON message content
monitor: increase amount of data for monitor to read
Vladimir Sementsov-Ogievskiy (1):
iotests: 129 don't check backup "busy"
include/qapi/qmp/json-parser.h | 5 ++--
monitor/monitor.c | 2 +-
monitor/qmp.c | 66 ++++++++++++++++++++++++------------------
qga/main.c | 2 +-
qobject/json-lexer.c | 30 +++++++++++++------
qobject/json-parser-int.h | 8 +++--
qobject/json-streamer.c | 15 +++++-----
qobject/qjson.c | 2 +-
tests/qemu-iotests/129 | 1 -
tests/qtest/libqtest.c | 2 +-
10 files changed, 79 insertions(+), 54 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-11-27 13:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 13:35 Andrey Shinkevich via [this message]
2020-11-27 13:35 ` [PATCH v3 1/5] monitor: change function obsolete name in comments Andrey Shinkevich via
2021-03-02 13:45 ` Markus Armbruster
2020-11-27 13:35 ` [PATCH v3 2/5] monitor: drain requests queue with 'channel closed' event Andrey Shinkevich via
2021-03-02 13:53 ` Markus Armbruster
2021-03-02 15:25 ` Vladimir Sementsov-Ogievskiy
2021-03-02 16:32 ` Denis V. Lunev
2021-03-02 17:02 ` Vladimir Sementsov-Ogievskiy
2021-03-05 13:41 ` Markus Armbruster
2021-03-05 14:01 ` Vladimir Sementsov-Ogievskiy
2020-11-27 13:35 ` [PATCH v3 3/5] monitor: let QMP monitor track JSON message content Andrey Shinkevich via
2020-11-27 13:35 ` [PATCH v3 4/5] iotests: 129 don't check backup "busy" Andrey Shinkevich via
2021-03-02 13:45 ` Markus Armbruster
2020-11-27 13:35 ` [PATCH v3 5/5] monitor: increase amount of data for monitor to read Andrey Shinkevich via
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=1606484146-913540-1-git-send-email-andrey.shinkevich@virtuozzo.com \
--to=qemu-devel@nongnu.org \
--cc=andrey.shinkevich@virtuozzo.com \
--cc=armbru@redhat.com \
--cc=den@openvz.org \
--cc=dgilbert@redhat.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=thuth@redhat.com \
--cc=vsementsov@virtuozzo.com \
/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.