Le Wednesday 29 Jan 2014 à 16:40:43 (+0800), Fam Zheng a écrit :
> This case utilizes qemu-io command "aio_{read,write} -a -q" to verify
> the effectiveness of IO throttling options.
>
> The "-a" option will cause qemu-io requests to be accounted.
>
> It's implemented by driving the vm timer from
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
> +retu
On Wed, Jan 29, 2014 at 04:40:43PM +0800, Fam Zheng wrote:
> This case utilizes qemu-io command "aio_{read,write} -a -q" to verify
> the effectiveness of IO throttling options.
>
> The "-a" option will cause qemu-io requests to be accounted.
>
> It's implemented by driving the vm timer from qtest
This case utilizes qemu-io command "aio_{read,write} -a -q" to verify
the effectiveness of IO throttling options.
The "-a" option will cause qemu-io requests to be accounted.
It's implemented by driving the vm timer from qtest protocol, so the
throttling timers are signaled with determinied time
