2005-11-04 08:43:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-05-19 08:16:41 -06:00
|
|
|
|
2010-09-03 11:56:16 +02:00
|
|
|
|
2008-09-14 05:55:09 -07:00
|
|
|
|
2016-11-07 21:32:37 -07:00
|
|
|
|
2017-01-17 06:03:22 -07:00
|
|
|
|
2017-01-28 09:32:51 +01:00
|
|
|
|
2015-12-24 19:20:32 -07:00
|
|
|
|
2005-11-04 08:43:35 +01:00
|
|
|
|
2017-01-28 09:32:51 +01:00
|
|
|
|
|
|
|
|
|
2007-07-09 12:38:05 +02:00
|
|
|
|
2011-07-31 22:05:09 +02:00
|
|
|
|
2009-12-03 12:59:42 -05:00
|
|
|
|
2010-09-15 17:06:35 -04:00
|
|
|
|
2005-11-04 08:43:35 +01:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2017-01-14 17:11:11 -07:00
|
|
|
|
2006-03-23 20:00:26 +01:00
|
|
|
|
2007-10-12 12:50:41 +02:00
|
|
|
|
2013-09-30 13:45:19 -07:00
|
|
|
|
2014-09-26 19:20:07 -04:00
|
|
|
|
2016-09-19 15:50:16 +10:00
|
|
|
|
2017-02-05 18:15:24 +01:00
|
|
|
|
2016-10-18 15:40:33 +09:00
|
|
|
|
blk-wbt: add general throttling mechanism
We can hook this up to the block layer, to help throttle buffered
writes.
wbt registers a few trace points that can be used to track what is
happening in the system:
wbt_lat: 259:0: latency 2446318
wbt_stat: 259:0: rmean=2446318, rmin=2446318, rmax=2446318, rsamples=1,
wmean=518866, wmin=15522, wmax=5330353, wsamples=57
wbt_step: 259:0: step down: step=1, window=72727272, background=8, normal=16, max=32
This shows a sync issue event (wbt_lat) that exceeded it's time. wbt_stat
dumps the current read/write stats for that window, and wbt_step shows a
step down event where we now scale back writes. Each trace includes the
device, 259:0 in this case.
Signed-off-by: Jens Axboe <axboe@fb.com>
2016-11-09 12:36:15 -07:00
|
|
|
|
2017-01-27 15:03:01 -07:00
|
|
|
|
2017-02-03 12:50:31 -07:00
|
|
|
|