Fam Zheng writes:
> On Tue, 01/27 11:14, Max Reitz wrote:
>> On 2015-01-26 at 22:03, Fam Zheng wrote:
>> >On Mon, 01/26 15:45, Max Reitz wrote:
>> >>On 2015-01-16 at 03:46, Fam Zheng wrote:
>> >>>This case utilizes qemu-io command "aio_{read,write} -q" to verify the
>> >>>effectiveness of IO thro
On Tue, 01/27 11:14, Max Reitz wrote:
> On 2015-01-26 at 22:03, Fam Zheng wrote:
> >On Mon, 01/26 15:45, Max Reitz wrote:
> >>On 2015-01-16 at 03:46, Fam Zheng wrote:
> >>>This case utilizes qemu-io command "aio_{read,write} -q" to verify the
> >>>effectiveness of IO throttling options.
> >>>
> >>>
On 2015-01-26 at 22:03, Fam Zheng wrote:
On Mon, 01/26 15:45, Max Reitz wrote:
On 2015-01-16 at 03:46, 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, s
On Mon, 01/26 15:45, Max Reitz wrote:
> On 2015-01-16 at 03:46, 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
On 2015-01-16 at 03:46, 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
veri
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%
