From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: stefanha@redhat.com, kwolf@redhat.com, armbru@redhat.com,
mreitz@redhat.com, eblake@redhat.com, famz@redhat.com,
danpb@redhat.com
Cc: qemu-devel@nongnu.org, izumi.taku@jp.fujitsu.com,
caoj.fnst@cn.fujitsu.com, fanc.fnst@cn.fujitsu.com,
Dou Liyang <douly.fnst@cn.fujitsu.com>
Subject: [Qemu-devel] [PATCH v4 0/2] block/qapi: refactor and optimize the qmp_query_blockstats()
Date: Sun, 15 Jan 2017 16:01:13 +0800 [thread overview]
Message-ID: <1484467275-27919-1-git-send-email-douly.fnst@cn.fujitsu.com> (raw)
Change log v3 -> v4:
1. Develop these into the non-RFC patches.
2. Fix some comments.
3. do declarations first.
Change log v2 -> v3:
1. Remove the unnecessary code for the bdrv_next_node().
2. Remove the change of the locking rules.
Even if this change can improve the performance, but it may
effect the consistency.
The Qemu uses the qmp_query_blockstats() function to get the
blockstats. As the function has been changed several times, it
becomes more complex and longer.
For the multi-disks guest, if we want to execute I/O operations
and this function at the same time. we can use the dataplane
feature to hold I/O performance does not drop. But, Normally
without this feature, How to reduce the decline in performance?
These patches refactor the qmp_query_blockstats() to make the
code easier to follow, and shorter as follows:
From:
+--------------+ +---------------------+
| 1 | | 4. |
|next_query_bds| |bdrv_query_bds_stats +---+
| | | | |
+--------^-----+ +-------------^-------+ |
| | |
+---------+----------+ +--------+-------+ |
| 0. | | 2. | |
|qmp_query_blockstats+------>bdrv_query_stats<----
| | | |
+--------------------+ +--------+-------+
|
+-------------v-------+
| 3. |
|bdrv_query_blk_stats |
| |
+---------------------+
To:
+--------------+
| |
+--------v-----------+ |
+---> 3. | |
+-------------------+ | |bdrv_query_bds_stats+--+
| 1. +--+ | |
| + +--------------------+
|qmp_query_blockstats--+
| | |
+-------------------+ | +--------------------+
| | 2. |
+---> |
|bdrv_query_blk_stats|
| |
+--------------------+
They also optimize the fuction by reducing its running time.
1. The function running time
the time it takes(ns) in each requests:
the disk numbers | 10 | 500
-------------------------------------
before these patches | 19429 | 667722
after these patches | 18536 | 627945
2. For the performance
used the dd command likes this to test:
dd if=date_1.dat of=date_2.dat conv=fsync oflag=direct bs=1k count=100k.
the I/O performance is degraded(%) during the monitor:
the disk numbers | 10 | 500
-------------------------------------
before these patches | 1.3 | 14.2
after these patches | 1.0 | 11.3
Dou Liyang (2):
block/qapi: reduce the coupling between the bdrv_query_stats and
bdrv_query_bds_stats
block/qapi: reduce the execution time of qmp_query_blockstats
block/qapi.c | 95 ++++++++++++++++++++++++++----------------------------------
1 file changed, 41 insertions(+), 54 deletions(-)
--
2.5.5
next reply other threads:[~2017-01-15 8:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 8:01 Dou Liyang [this message]
2017-01-15 8:01 ` [Qemu-devel] [PATCH v4 1/2] block/qapi: reduce the coupling between the bdrv_query_stats and bdrv_query_bds_stats Dou Liyang
2017-01-15 8:01 ` [Qemu-devel] [PATCH v4 2/2] block/qapi: reduce the execution time of qmp_query_blockstats Dou Liyang
2017-02-01 3:02 ` Max Reitz
2017-02-01 3:19 ` Dou Liyang
2017-01-23 5:31 ` [Qemu-devel] [PATCH v4 0/2] block/qapi: refactor and optimize the qmp_query_blockstats() Dou Liyang
2017-01-23 13:13 ` Markus Armbruster
2017-02-01 3:06 ` Max Reitz
2017-02-01 6:55 ` 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=1484467275-27919-1-git-send-email-douly.fnst@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=armbru@redhat.com \
--cc=caoj.fnst@cn.fujitsu.com \
--cc=danpb@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=izumi.taku@jp.fujitsu.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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).