diff options
author | Stefan Hajnoczi <stefanha@redhat.com> | 2013-04-05 11:32:20 +0200 |
---|---|---|
committer | Kevin Wolf <kwolf@redhat.com> | 2013-04-05 18:58:05 +0200 |
commit | ae29d6c64bd8d55873a2cb1df50ae4321b497447 (patch) | |
tree | d677532c07fcb19a2f6708eecaa185f63e92d8da /include/block | |
parent | 5905fbc9c94ccd744c1b249472eafcc2d827548a (diff) |
block: keep I/O throttling slice time constant
It is not necessary to adjust the slice time at runtime. We already
extend the current slice in order to carry over accounting into the next
slice. Changing the actual slice time value introduces oscillations.
The guest may experience large changes in throughput or IOPS from one
moment to the next when slice times are adjusted.
Reported-by: BenoƮt Canet <benoit@irqsave.net>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Tested-By: Benoit Canet <benoit@irqsave.net>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'include/block')
-rw-r--r-- | include/block/block_int.h | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/include/block/block_int.h b/include/block/block_int.h index 83941d8672..9aa98b5d12 100644 --- a/include/block/block_int.h +++ b/include/block/block_int.h @@ -252,7 +252,6 @@ struct BlockDriverState { unsigned int copy_on_read_in_flight; /* the time for latest disk I/O */ - int64_t slice_time; int64_t slice_start; int64_t slice_end; BlockIOLimit io_limits; |