If op_size is non-zero, iops limits are merely a fixed proportion of bps
limits, which means the lower set of the two is applied and the higher
skipped.
I understand the amazon uses op_size like accounting for big IO requests, but
we don't do it condionally on io size or anything here, so
Il 02/09/2013 12:16, Benoît Canet ha scritto:
If op_size is non-zero, iops limits are merely a fixed proportion of bps
limits, which means the lower set of the two is applied and the higher
skipped.
I understand the amazon uses op_size like accounting for big IO requests,
but
we don't
However, I think this is not what the code is doing right now, isn't it?
Hi Paolo,
I changed the code so it trigger only if the request size is bigger than
op_size.
Best regards
Benoît
Implement the continuous leaky bucket algorithm devised on IRC as a separate
module.
Signed-off-by: Benoit Canet ben...@irqsave.net
---
include/qemu/throttle.h | 103
util/Makefile.objs |1 +
util/throttle.c | 396 +++
3
On Sun, 09/01 18:39, Benoît Canet wrote:
Implement the continuous leaky bucket algorithm devised on IRC as a separate
module.
Signed-off-by: Benoit Canet ben...@irqsave.net
---
include/qemu/throttle.h | 103
util/Makefile.objs |1 +
util/throttle.c | 396
