On 2015-01-29 at 21:49, Fam Zheng wrote:
This case utilizes qemu-io command "aio_{read,write} -q" to verify the effectiveness of IO throttling options.It's implemented by driving the vm timer from qtest protocol, so the throttling timers are signaled with determinied time duration. Then we verify the completed IO requests are within 10% error of bps and iops limits. "null" protocol is used as the disk backend so that no actual disk IO is performed on host, this will make the blockstats much more deterministic. Both "null-aio" and "null-co" are covered, which is also a simple cross validation test for the driver code. Signed-off-by: Fam Zheng <f...@redhat.com> --- tests/qemu-iotests/093 | 114 +++++++++++++++++++++++++++++++++++++++++++++ tests/qemu-iotests/093.out | 5 ++ tests/qemu-iotests/group | 1 + 3 files changed, 120 insertions(+) create mode 100755 tests/qemu-iotests/093 create mode 100644 tests/qemu-iotests/093.out
Reviewed-by: Max Reitz <mre...@redhat.com>
