[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-block] [Qemu-devel] Consistency of iotests 093 and 136

From: Markus Armbruster
Subject: Re: [Qemu-block] [Qemu-devel] Consistency of iotests 093 and 136
Date: Tue, 29 Jan 2019 13:11:07 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

Alberto Garcia <address@hidden> writes:

> On Mon 28 Jan 2019 07:38:08 PM CET, Markus Armbruster wrote:
>>> 093 submits several I/O requests using aio_read and aio_write with
>>> hmp_qemu_io(), then advances the clock using clock_step and finally
>>> calls query-blockstats to see how much of the I/O has been completed
>>> (it's an I/O throttling test).
>>> The expectation is that by the time query-blockstats is called all
>>> submitted I/O requests have been processed (up to the amount allowed
>>> by the throttling limits).
>> Assumptions like "when we see the reply to QMP command X, surely the
>> main loop has completed doing Y" are problematic.  When possible, rely
>> on something more direct, such as a query command that shows you
>> whether Y has been completed.
> Right, but how to do that for aio_read / aio_write ?

Fair question.

What exactly do you need to wait for?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]