summaryrefslogtreecommitdiffstats
path: root/tools/objtool/check.c
diff options
context:
space:
mode:
authorJosef Bacik <josef@toxicpanda.com>2018-09-28 13:45:43 -0400
committerJens Axboe <axboe@kernel.dk>2018-09-28 11:47:32 -0600
commit451bb7c3319739997d2e5a2527aef62d1f9200ac (patch)
tree93d5da9e9d960a47b57a1fe661c3be6a34aa4be2 /tools/objtool/check.c
parent1fa2840e56f9032e14a75fcf67edfe0f21102e4b (diff)
downloadblackbird-obmc-linux-451bb7c3319739997d2e5a2527aef62d1f9200ac.tar.gz
blackbird-obmc-linux-451bb7c3319739997d2e5a2527aef62d1f9200ac.zip
blk-iolatency: keep track of previous windows stats
We apply a smoothing to the scale changes in order to keep sawtoothy behavior from occurring. However our window for checking if we've missed our target can sometimes be lower than the smoothing interval (500ms), especially on faster drives like ssd's. In order to deal with this keep track of the running tally of the previous intervals that we threw away because we had already done a scale event recently. This is needed for the ssd case as these low latency drives will have bursts of latency, and if it happens to be ok for the window that directly follows the opening of the scale window we could unthrottle when previous windows we were missing our target. Signed-off-by: Josef Bacik <josef@toxicpanda.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/objtool/check.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud