From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Benoît Canet" <benoit.canet@irqsave.net>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4/4] qemu-iotests: Add 080 for IO throttling
Date: Wed, 29 Jan 2014 15:45:08 +0100 [thread overview]
Message-ID: <20140129144508.GH23531@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <1390984843-2101-5-git-send-email-famz@redhat.com>
On Wed, Jan 29, 2014 at 04:40:43PM +0800, Fam Zheng wrote:
> + def do_test_throttle(self, seconds=10, **limits):
> + def check_limit(limit, num):
> + # IO throttling algorithm is discrete, allow 10% error so the test
> + # is more deterministic
> + return limit == 0 or num < seconds * limit * 1.1
> +
> + nsec_per_sec = 1000000000
> +
> + limits['bps_max'] = 1
> + limits['iops_max'] = 1
> +
> + # Enqueue many requests to throttling queue
> + result = self.vm.qmp("block_set_io_throttle", conv_keys=False, **limits)
> + self.assert_qmp(result, 'return', {})
> +
> + # Set vm clock to a known value
> + ns = nsec_per_sec
> + self.vm.qtest_cmd("clock_step %d" % ns)
> +
> + # Append many requests into the throttle queue
> + # They drain bps_max and iops_max
> + # The rest requests won't get executed until qtest clock is driven
> + for i in range(1000):
> + self.vm.hmp_qemu_io("drive0", "aio_read -a -q 0 512")
> + self.vm.hmp_qemu_io("drive0", "aio_write -a -q 0 512")
> +
> + start_rd_bytes, start_rd_iops, start_wr_bytes, start_wr_iops = self.blockstats('drive0')
> +
> + ns += seconds * nsec_per_sec
> + self.vm.qtest_cmd("clock_step %d" % ns)
> + # wait for a while to let requests take off
> + time.sleep(1)
> + end_rd_bytes, end_rd_iops, end_wr_bytes, end_wr_iops = self.blockstats('drive0')
> +
> + rd_bytes = end_rd_bytes - start_rd_bytes
> + rd_iops = end_rd_iops - start_rd_iops
> + wr_bytes = end_wr_bytes - start_wr_bytes
> + wr_iops = end_wr_iops - start_wr_iops
> +
> + assert check_limit(limits['bps'], rd_bytes)
> + assert check_limit(limits['bps_rd'], rd_bytes)
> + assert check_limit(limits['bps'], wr_bytes)
> + assert check_limit(limits['bps_wr'], wr_bytes)
> + assert check_limit(limits['iops'], rd_iops)
> + assert check_limit(limits['iops_rd'], rd_iops)
> + assert check_limit(limits['iops'], wr_iops)
> + assert check_limit(limits['iops_wr'], wr_iops)
> +
> + def test_bps(self):
> + self.do_test_throttle(**{
> + 'device': 'drive0',
> + 'bps': 1000,
> + 'bps_rd': 0,
> + 'bps_wr': 0,
> + 'iops': 0,
> + 'iops_rd': 0,
> + 'iops_wr': 0,
> + })
> +
> + def test_bps_rd(self):
> + self.do_test_throttle(**{
> + 'device': 'drive0',
> + 'bps': 0,
> + 'bps_rd': 1000,
> + 'bps_wr': 0,
> + 'iops': 0,
> + 'iops_rd': 0,
> + 'iops_wr': 0,
> + })
I guess you'll get more stable behavior with 1024 instead of 1000. The
request themselves are 512 bytes.
As a side note, I think we'll wait for all 1000 pending requests each
time QEMU shuts down. Probably not a huge time waste but even 100
requests exceed the I/O limits you've specified. Perhaps using just 100
will make the test slightly faster.
next prev parent reply other threads:[~2014-01-29 14:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 8:40 [Qemu-devel] [PATCH 0/4] qemu-iotests: Test case for IO throttling Fam Zheng
2014-01-29 8:40 ` [Qemu-devel] [PATCH 1/4] qemu-io: New option "-a" to aio_read and aio_write Fam Zheng
2014-01-29 14:11 ` Stefan Hajnoczi
2014-01-29 15:25 ` Benoît Canet
2014-01-29 15:58 ` Paolo Bonzini
2014-02-01 14:31 ` Fam Zheng
2014-02-02 0:20 ` Paolo Bonzini
2014-02-07 7:47 ` Fam Zheng
2014-01-29 8:40 ` [Qemu-devel] [PATCH 2/4] qemu-iotests: Add VM method qtest_cmd() to iotests.py Fam Zheng
2014-01-29 14:22 ` Stefan Hajnoczi
2014-02-01 15:23 ` Fam Zheng
2014-01-29 8:40 ` [Qemu-devel] [PATCH 3/4] qemu-iotests: Allow caller to disable underscore convertion for qmp Fam Zheng
2014-01-29 14:09 ` Eric Blake
2014-02-01 15:31 ` Fam Zheng
2014-01-29 14:23 ` Stefan Hajnoczi
2014-01-29 15:29 ` Benoît Canet
2014-01-29 8:40 ` [Qemu-devel] [PATCH 4/4] qemu-iotests: Add 080 for IO throttling Fam Zheng
2014-01-29 14:36 ` Stefan Hajnoczi
2014-01-29 14:45 ` Stefan Hajnoczi [this message]
2014-01-29 15:34 ` Benoît Canet
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=20140129144508.GH23531@stefanha-thinkpad.muc.redhat.com \
--to=stefanha@redhat.com \
--cc=benoit.canet@irqsave.net \
--cc=famz@redhat.com \
--cc=kwolf@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 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).