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 22:36:15 +03:00
|
|
|
/*
|
|
|
|
* buffered writeback throttling. loosely based on CoDel. We can't drop
|
|
|
|
* packets for IO scheduling, so the logic is something like this:
|
|
|
|
*
|
|
|
|
* - Monitor latencies in a defined window of time.
|
|
|
|
* - If the minimum latency in the above window exceeds some target, increment
|
|
|
|
* scaling step and scale down queue depth by a factor of 2x. The monitoring
|
|
|
|
* window is then shrunk to 100 / sqrt(scaling step + 1).
|
|
|
|
* - For any window where we don't have solid data on what the latencies
|
|
|
|
* look like, retain status quo.
|
|
|
|
* - If latencies look good, decrement scaling step.
|
|
|
|
* - If we're only doing writes, allow the scaling step to go negative. This
|
|
|
|
* will temporarily boost write performance, snapping back to a stable
|
|
|
|
* scaling step of 0 if reads show up or the heavy writers finish. Unlike
|
|
|
|
* positive scaling steps where we shrink the monitoring window, a negative
|
|
|
|
* scaling step retains the default step==0 window size.
|
|
|
|
*
|
|
|
|
* Copyright (C) 2016 Jens Axboe
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
#include <linux/blk_types.h>
|
|
|
|
#include <linux/slab.h>
|
|
|
|
#include <linux/backing-dev.h>
|
|
|
|
#include <linux/swap.h>
|
|
|
|
|
|
|
|
#include "blk-wbt.h"
|
|
|
|
|
|
|
|
#define CREATE_TRACE_POINTS
|
|
|
|
#include <trace/events/wbt.h>
|
|
|
|
|
|
|
|
enum {
|
|
|
|
/*
|
|
|
|
* Default setting, we'll scale up (to 75% of QD max) or down (min 1)
|
|
|
|
* from here depending on device stats
|
|
|
|
*/
|
|
|
|
RWB_DEF_DEPTH = 16,
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 100msec window
|
|
|
|
*/
|
|
|
|
RWB_WINDOW_NSEC = 100 * 1000 * 1000ULL,
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Disregard stats, if we don't meet this minimum
|
|
|
|
*/
|
|
|
|
RWB_MIN_WRITE_SAMPLES = 3,
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If we have this number of consecutive windows with not enough
|
|
|
|
* information to scale up or down, scale up.
|
|
|
|
*/
|
|
|
|
RWB_UNKNOWN_BUMP = 5,
|
|
|
|
};
|
|
|
|
|
|
|
|
static inline bool rwb_enabled(struct rq_wb *rwb)
|
|
|
|
{
|
|
|
|
return rwb && rwb->wb_normal != 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Increment 'v', if 'v' is below 'below'. Returns true if we succeeded,
|
|
|
|
* false if 'v' + 1 would be bigger than 'below'.
|
|
|
|
*/
|
|
|
|
static bool atomic_inc_below(atomic_t *v, int below)
|
|
|
|
{
|
|
|
|
int cur = atomic_read(v);
|
|
|
|
|
|
|
|
for (;;) {
|
|
|
|
int old;
|
|
|
|
|
|
|
|
if (cur >= below)
|
|
|
|
return false;
|
|
|
|
old = atomic_cmpxchg(v, cur, cur + 1);
|
|
|
|
if (old == cur)
|
|
|
|
break;
|
|
|
|
cur = old;
|
|
|
|
}
|
|
|
|
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void wb_timestamp(struct rq_wb *rwb, unsigned long *var)
|
|
|
|
{
|
|
|
|
if (rwb_enabled(rwb)) {
|
|
|
|
const unsigned long cur = jiffies;
|
|
|
|
|
|
|
|
if (cur != *var)
|
|
|
|
*var = cur;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If a task was rate throttled in balance_dirty_pages() within the last
|
|
|
|
* second or so, use that to indicate a higher cleaning rate.
|
|
|
|
*/
|
|
|
|
static bool wb_recent_wait(struct rq_wb *rwb)
|
|
|
|
{
|
2017-02-02 17:56:50 +03:00
|
|
|
struct bdi_writeback *wb = &rwb->queue->backing_dev_info->wb;
|
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 22:36:15 +03:00
|
|
|
|
|
|
|
return time_before(jiffies, wb->dirty_sleep + HZ);
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline struct rq_wait *get_rq_wait(struct rq_wb *rwb, bool is_kswapd)
|
|
|
|
{
|
|
|
|
return &rwb->rq_wait[is_kswapd];
|
|
|
|
}
|
|
|
|
|
|
|
|
static void rwb_wake_all(struct rq_wb *rwb)
|
|
|
|
{
|
|
|
|
int i;
|
|
|
|
|
|
|
|
for (i = 0; i < WBT_NUM_RWQ; i++) {
|
|
|
|
struct rq_wait *rqw = &rwb->rq_wait[i];
|
|
|
|
|
|
|
|
if (waitqueue_active(&rqw->wait))
|
|
|
|
wake_up_all(&rqw->wait);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void __wbt_done(struct rq_wb *rwb, enum wbt_flags wb_acct)
|
|
|
|
{
|
|
|
|
struct rq_wait *rqw;
|
|
|
|
int inflight, limit;
|
|
|
|
|
|
|
|
if (!(wb_acct & WBT_TRACKED))
|
|
|
|
return;
|
|
|
|
|
|
|
|
rqw = get_rq_wait(rwb, wb_acct & WBT_KSWAPD);
|
|
|
|
inflight = atomic_dec_return(&rqw->inflight);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* wbt got disabled with IO in flight. Wake up any potential
|
|
|
|
* waiters, we don't have to do more than that.
|
|
|
|
*/
|
|
|
|
if (unlikely(!rwb_enabled(rwb))) {
|
|
|
|
rwb_wake_all(rwb);
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If the device does write back caching, drop further down
|
|
|
|
* before we wake people up.
|
|
|
|
*/
|
|
|
|
if (rwb->wc && !wb_recent_wait(rwb))
|
|
|
|
limit = 0;
|
|
|
|
else
|
|
|
|
limit = rwb->wb_normal;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Don't wake anyone up if we are above the normal limit.
|
|
|
|
*/
|
|
|
|
if (inflight && inflight >= limit)
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (waitqueue_active(&rqw->wait)) {
|
|
|
|
int diff = limit - inflight;
|
|
|
|
|
|
|
|
if (!inflight || diff >= rwb->wb_background / 2)
|
|
|
|
wake_up_all(&rqw->wait);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Called on completion of a request. Note that it's also called when
|
|
|
|
* a request is merged, when the request gets freed.
|
|
|
|
*/
|
|
|
|
void wbt_done(struct rq_wb *rwb, struct blk_issue_stat *stat)
|
|
|
|
{
|
|
|
|
if (!rwb)
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (!wbt_is_tracked(stat)) {
|
|
|
|
if (rwb->sync_cookie == stat) {
|
|
|
|
rwb->sync_issue = 0;
|
|
|
|
rwb->sync_cookie = NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (wbt_is_read(stat))
|
|
|
|
wb_timestamp(rwb, &rwb->last_comp);
|
|
|
|
} else {
|
|
|
|
WARN_ON_ONCE(stat == rwb->sync_cookie);
|
|
|
|
__wbt_done(rwb, wbt_stat_to_mask(stat));
|
|
|
|
}
|
2017-11-23 16:39:55 +03:00
|
|
|
wbt_clear_state(stat);
|
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 22:36:15 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Return true, if we can't increase the depth further by scaling
|
|
|
|
*/
|
|
|
|
static bool calc_wb_limits(struct rq_wb *rwb)
|
|
|
|
{
|
|
|
|
unsigned int depth;
|
|
|
|
bool ret = false;
|
|
|
|
|
|
|
|
if (!rwb->min_lat_nsec) {
|
|
|
|
rwb->wb_max = rwb->wb_normal = rwb->wb_background = 0;
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* For QD=1 devices, this is a special case. It's important for those
|
|
|
|
* to have one request ready when one completes, so force a depth of
|
|
|
|
* 2 for those devices. On the backend, it'll be a depth of 1 anyway,
|
|
|
|
* since the device can't have more than that in flight. If we're
|
|
|
|
* scaling down, then keep a setting of 1/1/1.
|
|
|
|
*/
|
|
|
|
if (rwb->queue_depth == 1) {
|
|
|
|
if (rwb->scale_step > 0)
|
|
|
|
rwb->wb_max = rwb->wb_normal = 1;
|
|
|
|
else {
|
|
|
|
rwb->wb_max = rwb->wb_normal = 2;
|
|
|
|
ret = true;
|
|
|
|
}
|
|
|
|
rwb->wb_background = 1;
|
|
|
|
} else {
|
|
|
|
/*
|
|
|
|
* scale_step == 0 is our default state. If we have suffered
|
|
|
|
* latency spikes, step will be > 0, and we shrink the
|
|
|
|
* allowed write depths. If step is < 0, we're only doing
|
|
|
|
* writes, and we allow a temporarily higher depth to
|
|
|
|
* increase performance.
|
|
|
|
*/
|
|
|
|
depth = min_t(unsigned int, RWB_DEF_DEPTH, rwb->queue_depth);
|
|
|
|
if (rwb->scale_step > 0)
|
|
|
|
depth = 1 + ((depth - 1) >> min(31, rwb->scale_step));
|
|
|
|
else if (rwb->scale_step < 0) {
|
|
|
|
unsigned int maxd = 3 * rwb->queue_depth / 4;
|
|
|
|
|
|
|
|
depth = 1 + ((depth - 1) << -rwb->scale_step);
|
|
|
|
if (depth > maxd) {
|
|
|
|
depth = maxd;
|
|
|
|
ret = true;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Set our max/normal/bg queue depths based on how far
|
|
|
|
* we have scaled down (->scale_step).
|
|
|
|
*/
|
|
|
|
rwb->wb_max = depth;
|
|
|
|
rwb->wb_normal = (rwb->wb_max + 1) / 2;
|
|
|
|
rwb->wb_background = (rwb->wb_max + 3) / 4;
|
|
|
|
}
|
|
|
|
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2016-11-16 18:29:57 +03:00
|
|
|
static inline bool stat_sample_valid(struct blk_rq_stat *stat)
|
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 22:36:15 +03:00
|
|
|
{
|
|
|
|
/*
|
|
|
|
* We need at least one read sample, and a minimum of
|
|
|
|
* RWB_MIN_WRITE_SAMPLES. We require some write samples to know
|
|
|
|
* that it's writes impacting us, and not just some sole read on
|
|
|
|
* a device that is in a lower power state.
|
|
|
|
*/
|
2017-03-21 18:56:06 +03:00
|
|
|
return (stat[READ].nr_samples >= 1 &&
|
|
|
|
stat[WRITE].nr_samples >= RWB_MIN_WRITE_SAMPLES);
|
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 22:36:15 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
static u64 rwb_sync_issue_lat(struct rq_wb *rwb)
|
|
|
|
{
|
locking/atomics: COCCINELLE/treewide: Convert trivial ACCESS_ONCE() patterns to READ_ONCE()/WRITE_ONCE()
Please do not apply this to mainline directly, instead please re-run the
coccinelle script shown below and apply its output.
For several reasons, it is desirable to use {READ,WRITE}_ONCE() in
preference to ACCESS_ONCE(), and new code is expected to use one of the
former. So far, there's been no reason to change most existing uses of
ACCESS_ONCE(), as these aren't harmful, and changing them results in
churn.
However, for some features, the read/write distinction is critical to
correct operation. To distinguish these cases, separate read/write
accessors must be used. This patch migrates (most) remaining
ACCESS_ONCE() instances to {READ,WRITE}_ONCE(), using the following
coccinelle script:
----
// Convert trivial ACCESS_ONCE() uses to equivalent READ_ONCE() and
// WRITE_ONCE()
// $ make coccicheck COCCI=/home/mark/once.cocci SPFLAGS="--include-headers" MODE=patch
virtual patch
@ depends on patch @
expression E1, E2;
@@
- ACCESS_ONCE(E1) = E2
+ WRITE_ONCE(E1, E2)
@ depends on patch @
expression E;
@@
- ACCESS_ONCE(E)
+ READ_ONCE(E)
----
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: davem@davemloft.net
Cc: linux-arch@vger.kernel.org
Cc: mpe@ellerman.id.au
Cc: shuah@kernel.org
Cc: snitzer@redhat.com
Cc: thor.thayer@linux.intel.com
Cc: tj@kernel.org
Cc: viro@zeniv.linux.org.uk
Cc: will.deacon@arm.com
Link: http://lkml.kernel.org/r/1508792849-3115-19-git-send-email-paulmck@linux.vnet.ibm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2017-10-24 00:07:29 +03:00
|
|
|
u64 now, issue = READ_ONCE(rwb->sync_issue);
|
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 22:36:15 +03:00
|
|
|
|
|
|
|
if (!issue || !rwb->sync_cookie)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
now = ktime_to_ns(ktime_get());
|
|
|
|
return now - issue;
|
|
|
|
}
|
|
|
|
|
|
|
|
enum {
|
|
|
|
LAT_OK = 1,
|
|
|
|
LAT_UNKNOWN,
|
|
|
|
LAT_UNKNOWN_WRITES,
|
|
|
|
LAT_EXCEEDED,
|
|
|
|
};
|
|
|
|
|
blk-stat: convert to callback-based statistics reporting
Currently, statistics are gathered in ~0.13s windows, and users grab the
statistics whenever they need them. This is not ideal for both in-tree
users:
1. Writeback throttling wants its own dynamically sized window of
statistics. Since the blk-stats statistics are reset after every
window and the wbt windows don't line up with the blk-stats windows,
wbt doesn't see every I/O.
2. Polling currently grabs the statistics on every I/O. Again, depending
on how the window lines up, we may miss some I/Os. It's also
unnecessary overhead to get the statistics on every I/O; the hybrid
polling heuristic would be just as happy with the statistics from the
previous full window.
This reworks the blk-stats infrastructure to be callback-based: users
register a callback that they want called at a given time with all of
the statistics from the window during which the callback was active.
Users can dynamically bucketize the statistics. wbt and polling both
currently use read vs. write, but polling can be extended to further
subdivide based on request size.
The callbacks are kept on an RCU list, and each callback has percpu
stats buffers. There will only be a few users, so the overhead on the
I/O completion side is low. The stats flushing is also simplified
considerably: since the timer function is responsible for clearing the
statistics, we don't have to worry about stale statistics.
wbt is a trivial conversion. After the conversion, the windowing problem
mentioned above is fixed.
For polling, we register an extra callback that caches the previous
window's statistics in the struct request_queue for the hybrid polling
heuristic to use.
Since we no longer have a single stats buffer for the request queue,
this also removes the sysfs and debugfs stats entries. To replace those,
we add a debugfs entry for the poll statistics.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
2017-03-21 18:56:08 +03:00
|
|
|
static int latency_exceeded(struct rq_wb *rwb, struct blk_rq_stat *stat)
|
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 22:36:15 +03:00
|
|
|
{
|
2017-02-02 17:56:50 +03:00
|
|
|
struct backing_dev_info *bdi = rwb->queue->backing_dev_info;
|
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 22:36:15 +03:00
|
|
|
u64 thislat;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If our stored sync issue exceeds the window size, or it
|
|
|
|
* exceeds our min target AND we haven't logged any entries,
|
|
|
|
* flag the latency as exceeded. wbt works off completion latencies,
|
|
|
|
* but for a flooded device, a single sync IO can take a long time
|
|
|
|
* to complete after being issued. If this time exceeds our
|
|
|
|
* monitoring window AND we didn't see any other completions in that
|
|
|
|
* window, then count that sync IO as a violation of the latency.
|
|
|
|
*/
|
|
|
|
thislat = rwb_sync_issue_lat(rwb);
|
|
|
|
if (thislat > rwb->cur_win_nsec ||
|
2017-03-21 18:56:06 +03:00
|
|
|
(thislat > rwb->min_lat_nsec && !stat[READ].nr_samples)) {
|
2016-11-11 07:52:53 +03:00
|
|
|
trace_wbt_lat(bdi, thislat);
|
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 22:36:15 +03:00
|
|
|
return LAT_EXCEEDED;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* No read/write mix, if stat isn't valid
|
|
|
|
*/
|
|
|
|
if (!stat_sample_valid(stat)) {
|
|
|
|
/*
|
|
|
|
* If we had writes in this stat window and the window is
|
|
|
|
* current, we're only doing writes. If a task recently
|
|
|
|
* waited or still has writes in flights, consider us doing
|
|
|
|
* just writes as well.
|
|
|
|
*/
|
blk-stat: convert to callback-based statistics reporting
Currently, statistics are gathered in ~0.13s windows, and users grab the
statistics whenever they need them. This is not ideal for both in-tree
users:
1. Writeback throttling wants its own dynamically sized window of
statistics. Since the blk-stats statistics are reset after every
window and the wbt windows don't line up with the blk-stats windows,
wbt doesn't see every I/O.
2. Polling currently grabs the statistics on every I/O. Again, depending
on how the window lines up, we may miss some I/Os. It's also
unnecessary overhead to get the statistics on every I/O; the hybrid
polling heuristic would be just as happy with the statistics from the
previous full window.
This reworks the blk-stats infrastructure to be callback-based: users
register a callback that they want called at a given time with all of
the statistics from the window during which the callback was active.
Users can dynamically bucketize the statistics. wbt and polling both
currently use read vs. write, but polling can be extended to further
subdivide based on request size.
The callbacks are kept on an RCU list, and each callback has percpu
stats buffers. There will only be a few users, so the overhead on the
I/O completion side is low. The stats flushing is also simplified
considerably: since the timer function is responsible for clearing the
statistics, we don't have to worry about stale statistics.
wbt is a trivial conversion. After the conversion, the windowing problem
mentioned above is fixed.
For polling, we register an extra callback that caches the previous
window's statistics in the struct request_queue for the hybrid polling
heuristic to use.
Since we no longer have a single stats buffer for the request queue,
this also removes the sysfs and debugfs stats entries. To replace those,
we add a debugfs entry for the poll statistics.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
2017-03-21 18:56:08 +03:00
|
|
|
if (stat[WRITE].nr_samples || wb_recent_wait(rwb) ||
|
|
|
|
wbt_inflight(rwb))
|
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 22:36:15 +03:00
|
|
|
return LAT_UNKNOWN_WRITES;
|
|
|
|
return LAT_UNKNOWN;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If the 'min' latency exceeds our target, step down.
|
|
|
|
*/
|
2017-03-21 18:56:06 +03:00
|
|
|
if (stat[READ].min > rwb->min_lat_nsec) {
|
|
|
|
trace_wbt_lat(bdi, stat[READ].min);
|
2016-11-11 07:52:53 +03:00
|
|
|
trace_wbt_stat(bdi, stat);
|
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 22:36:15 +03:00
|
|
|
return LAT_EXCEEDED;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (rwb->scale_step)
|
2016-11-11 07:52:53 +03:00
|
|
|
trace_wbt_stat(bdi, stat);
|
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 22:36:15 +03:00
|
|
|
|
|
|
|
return LAT_OK;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void rwb_trace_step(struct rq_wb *rwb, const char *msg)
|
|
|
|
{
|
2017-02-02 17:56:50 +03:00
|
|
|
struct backing_dev_info *bdi = rwb->queue->backing_dev_info;
|
2016-11-11 07:52:53 +03:00
|
|
|
|
|
|
|
trace_wbt_step(bdi, msg, rwb->scale_step, rwb->cur_win_nsec,
|
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 22:36:15 +03:00
|
|
|
rwb->wb_background, rwb->wb_normal, rwb->wb_max);
|
|
|
|
}
|
|
|
|
|
|
|
|
static void scale_up(struct rq_wb *rwb)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* Hit max in previous round, stop here
|
|
|
|
*/
|
|
|
|
if (rwb->scaled_max)
|
|
|
|
return;
|
|
|
|
|
|
|
|
rwb->scale_step--;
|
|
|
|
rwb->unknown_cnt = 0;
|
|
|
|
|
|
|
|
rwb->scaled_max = calc_wb_limits(rwb);
|
|
|
|
|
|
|
|
rwb_wake_all(rwb);
|
|
|
|
|
|
|
|
rwb_trace_step(rwb, "step up");
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Scale rwb down. If 'hard_throttle' is set, do it quicker, since we
|
|
|
|
* had a latency violation.
|
|
|
|
*/
|
|
|
|
static void scale_down(struct rq_wb *rwb, bool hard_throttle)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* Stop scaling down when we've hit the limit. This also prevents
|
|
|
|
* ->scale_step from going to crazy values, if the device can't
|
|
|
|
* keep up.
|
|
|
|
*/
|
|
|
|
if (rwb->wb_max == 1)
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (rwb->scale_step < 0 && hard_throttle)
|
|
|
|
rwb->scale_step = 0;
|
|
|
|
else
|
|
|
|
rwb->scale_step++;
|
|
|
|
|
|
|
|
rwb->scaled_max = false;
|
|
|
|
rwb->unknown_cnt = 0;
|
|
|
|
calc_wb_limits(rwb);
|
|
|
|
rwb_trace_step(rwb, "step down");
|
|
|
|
}
|
|
|
|
|
|
|
|
static void rwb_arm_timer(struct rq_wb *rwb)
|
|
|
|
{
|
|
|
|
if (rwb->scale_step > 0) {
|
|
|
|
/*
|
|
|
|
* We should speed this up, using some variant of a fast
|
|
|
|
* integer inverse square root calculation. Since we only do
|
|
|
|
* this for every window expiration, it's not a huge deal,
|
|
|
|
* though.
|
|
|
|
*/
|
|
|
|
rwb->cur_win_nsec = div_u64(rwb->win_nsec << 4,
|
|
|
|
int_sqrt((rwb->scale_step + 1) << 8));
|
|
|
|
} else {
|
|
|
|
/*
|
|
|
|
* For step < 0, we don't want to increase/decrease the
|
|
|
|
* window size.
|
|
|
|
*/
|
|
|
|
rwb->cur_win_nsec = rwb->win_nsec;
|
|
|
|
}
|
|
|
|
|
blk-stat: convert to callback-based statistics reporting
Currently, statistics are gathered in ~0.13s windows, and users grab the
statistics whenever they need them. This is not ideal for both in-tree
users:
1. Writeback throttling wants its own dynamically sized window of
statistics. Since the blk-stats statistics are reset after every
window and the wbt windows don't line up with the blk-stats windows,
wbt doesn't see every I/O.
2. Polling currently grabs the statistics on every I/O. Again, depending
on how the window lines up, we may miss some I/Os. It's also
unnecessary overhead to get the statistics on every I/O; the hybrid
polling heuristic would be just as happy with the statistics from the
previous full window.
This reworks the blk-stats infrastructure to be callback-based: users
register a callback that they want called at a given time with all of
the statistics from the window during which the callback was active.
Users can dynamically bucketize the statistics. wbt and polling both
currently use read vs. write, but polling can be extended to further
subdivide based on request size.
The callbacks are kept on an RCU list, and each callback has percpu
stats buffers. There will only be a few users, so the overhead on the
I/O completion side is low. The stats flushing is also simplified
considerably: since the timer function is responsible for clearing the
statistics, we don't have to worry about stale statistics.
wbt is a trivial conversion. After the conversion, the windowing problem
mentioned above is fixed.
For polling, we register an extra callback that caches the previous
window's statistics in the struct request_queue for the hybrid polling
heuristic to use.
Since we no longer have a single stats buffer for the request queue,
this also removes the sysfs and debugfs stats entries. To replace those,
we add a debugfs entry for the poll statistics.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
2017-03-21 18:56:08 +03:00
|
|
|
blk_stat_activate_nsecs(rwb->cb, rwb->cur_win_nsec);
|
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 22:36:15 +03:00
|
|
|
}
|
|
|
|
|
blk-stat: convert to callback-based statistics reporting
Currently, statistics are gathered in ~0.13s windows, and users grab the
statistics whenever they need them. This is not ideal for both in-tree
users:
1. Writeback throttling wants its own dynamically sized window of
statistics. Since the blk-stats statistics are reset after every
window and the wbt windows don't line up with the blk-stats windows,
wbt doesn't see every I/O.
2. Polling currently grabs the statistics on every I/O. Again, depending
on how the window lines up, we may miss some I/Os. It's also
unnecessary overhead to get the statistics on every I/O; the hybrid
polling heuristic would be just as happy with the statistics from the
previous full window.
This reworks the blk-stats infrastructure to be callback-based: users
register a callback that they want called at a given time with all of
the statistics from the window during which the callback was active.
Users can dynamically bucketize the statistics. wbt and polling both
currently use read vs. write, but polling can be extended to further
subdivide based on request size.
The callbacks are kept on an RCU list, and each callback has percpu
stats buffers. There will only be a few users, so the overhead on the
I/O completion side is low. The stats flushing is also simplified
considerably: since the timer function is responsible for clearing the
statistics, we don't have to worry about stale statistics.
wbt is a trivial conversion. After the conversion, the windowing problem
mentioned above is fixed.
For polling, we register an extra callback that caches the previous
window's statistics in the struct request_queue for the hybrid polling
heuristic to use.
Since we no longer have a single stats buffer for the request queue,
this also removes the sysfs and debugfs stats entries. To replace those,
we add a debugfs entry for the poll statistics.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
2017-03-21 18:56:08 +03:00
|
|
|
static void wb_timer_fn(struct blk_stat_callback *cb)
|
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 22:36:15 +03:00
|
|
|
{
|
blk-stat: convert to callback-based statistics reporting
Currently, statistics are gathered in ~0.13s windows, and users grab the
statistics whenever they need them. This is not ideal for both in-tree
users:
1. Writeback throttling wants its own dynamically sized window of
statistics. Since the blk-stats statistics are reset after every
window and the wbt windows don't line up with the blk-stats windows,
wbt doesn't see every I/O.
2. Polling currently grabs the statistics on every I/O. Again, depending
on how the window lines up, we may miss some I/Os. It's also
unnecessary overhead to get the statistics on every I/O; the hybrid
polling heuristic would be just as happy with the statistics from the
previous full window.
This reworks the blk-stats infrastructure to be callback-based: users
register a callback that they want called at a given time with all of
the statistics from the window during which the callback was active.
Users can dynamically bucketize the statistics. wbt and polling both
currently use read vs. write, but polling can be extended to further
subdivide based on request size.
The callbacks are kept on an RCU list, and each callback has percpu
stats buffers. There will only be a few users, so the overhead on the
I/O completion side is low. The stats flushing is also simplified
considerably: since the timer function is responsible for clearing the
statistics, we don't have to worry about stale statistics.
wbt is a trivial conversion. After the conversion, the windowing problem
mentioned above is fixed.
For polling, we register an extra callback that caches the previous
window's statistics in the struct request_queue for the hybrid polling
heuristic to use.
Since we no longer have a single stats buffer for the request queue,
this also removes the sysfs and debugfs stats entries. To replace those,
we add a debugfs entry for the poll statistics.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
2017-03-21 18:56:08 +03:00
|
|
|
struct rq_wb *rwb = cb->data;
|
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 22:36:15 +03:00
|
|
|
unsigned int inflight = wbt_inflight(rwb);
|
|
|
|
int status;
|
|
|
|
|
blk-stat: convert to callback-based statistics reporting
Currently, statistics are gathered in ~0.13s windows, and users grab the
statistics whenever they need them. This is not ideal for both in-tree
users:
1. Writeback throttling wants its own dynamically sized window of
statistics. Since the blk-stats statistics are reset after every
window and the wbt windows don't line up with the blk-stats windows,
wbt doesn't see every I/O.
2. Polling currently grabs the statistics on every I/O. Again, depending
on how the window lines up, we may miss some I/Os. It's also
unnecessary overhead to get the statistics on every I/O; the hybrid
polling heuristic would be just as happy with the statistics from the
previous full window.
This reworks the blk-stats infrastructure to be callback-based: users
register a callback that they want called at a given time with all of
the statistics from the window during which the callback was active.
Users can dynamically bucketize the statistics. wbt and polling both
currently use read vs. write, but polling can be extended to further
subdivide based on request size.
The callbacks are kept on an RCU list, and each callback has percpu
stats buffers. There will only be a few users, so the overhead on the
I/O completion side is low. The stats flushing is also simplified
considerably: since the timer function is responsible for clearing the
statistics, we don't have to worry about stale statistics.
wbt is a trivial conversion. After the conversion, the windowing problem
mentioned above is fixed.
For polling, we register an extra callback that caches the previous
window's statistics in the struct request_queue for the hybrid polling
heuristic to use.
Since we no longer have a single stats buffer for the request queue,
this also removes the sysfs and debugfs stats entries. To replace those,
we add a debugfs entry for the poll statistics.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
2017-03-21 18:56:08 +03:00
|
|
|
status = latency_exceeded(rwb, cb->stat);
|
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 22:36:15 +03:00
|
|
|
|
2017-02-02 17:56:50 +03:00
|
|
|
trace_wbt_timer(rwb->queue->backing_dev_info, status, rwb->scale_step,
|
2016-11-11 07:52:53 +03:00
|
|
|
inflight);
|
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 22:36:15 +03:00
|
|
|
|
|
|
|
/*
|
|
|
|
* If we exceeded the latency target, step down. If we did not,
|
|
|
|
* step one level up. If we don't know enough to say either exceeded
|
|
|
|
* or ok, then don't do anything.
|
|
|
|
*/
|
|
|
|
switch (status) {
|
|
|
|
case LAT_EXCEEDED:
|
|
|
|
scale_down(rwb, true);
|
|
|
|
break;
|
|
|
|
case LAT_OK:
|
|
|
|
scale_up(rwb);
|
|
|
|
break;
|
|
|
|
case LAT_UNKNOWN_WRITES:
|
|
|
|
/*
|
|
|
|
* We started a the center step, but don't have a valid
|
|
|
|
* read/write sample, but we do have writes going on.
|
|
|
|
* Allow step to go negative, to increase write perf.
|
|
|
|
*/
|
|
|
|
scale_up(rwb);
|
|
|
|
break;
|
|
|
|
case LAT_UNKNOWN:
|
|
|
|
if (++rwb->unknown_cnt < RWB_UNKNOWN_BUMP)
|
|
|
|
break;
|
|
|
|
/*
|
|
|
|
* We get here when previously scaled reduced depth, and we
|
|
|
|
* currently don't have a valid read/write sample. For that
|
|
|
|
* case, slowly return to center state (step == 0).
|
|
|
|
*/
|
|
|
|
if (rwb->scale_step > 0)
|
|
|
|
scale_up(rwb);
|
|
|
|
else if (rwb->scale_step < 0)
|
|
|
|
scale_down(rwb, false);
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Re-arm timer, if we have IO in flight
|
|
|
|
*/
|
|
|
|
if (rwb->scale_step || inflight)
|
|
|
|
rwb_arm_timer(rwb);
|
|
|
|
}
|
|
|
|
|
|
|
|
void wbt_update_limits(struct rq_wb *rwb)
|
|
|
|
{
|
|
|
|
rwb->scale_step = 0;
|
|
|
|
rwb->scaled_max = false;
|
|
|
|
calc_wb_limits(rwb);
|
|
|
|
|
|
|
|
rwb_wake_all(rwb);
|
|
|
|
}
|
|
|
|
|
|
|
|
static bool close_io(struct rq_wb *rwb)
|
|
|
|
{
|
|
|
|
const unsigned long now = jiffies;
|
|
|
|
|
|
|
|
return time_before(now, rwb->last_issue + HZ / 10) ||
|
|
|
|
time_before(now, rwb->last_comp + HZ / 10);
|
|
|
|
}
|
|
|
|
|
|
|
|
#define REQ_HIPRIO (REQ_SYNC | REQ_META | REQ_PRIO)
|
|
|
|
|
|
|
|
static inline unsigned int get_limit(struct rq_wb *rwb, unsigned long rw)
|
|
|
|
{
|
|
|
|
unsigned int limit;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* At this point we know it's a buffered write. If this is
|
2017-11-23 16:40:10 +03:00
|
|
|
* kswapd trying to free memory, or REQ_SYNC is set, then
|
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 22:36:15 +03:00
|
|
|
* it's WB_SYNC_ALL writeback, and we'll use the max limit for
|
|
|
|
* that. If the write is marked as a background write, then use
|
|
|
|
* the idle limit, or go to normal if we haven't had competing
|
|
|
|
* IO for a bit.
|
|
|
|
*/
|
|
|
|
if ((rw & REQ_HIPRIO) || wb_recent_wait(rwb) || current_is_kswapd())
|
|
|
|
limit = rwb->wb_max;
|
|
|
|
else if ((rw & REQ_BACKGROUND) || close_io(rwb)) {
|
|
|
|
/*
|
|
|
|
* If less than 100ms since we completed unrelated IO,
|
|
|
|
* limit us to half the depth for background writeback.
|
|
|
|
*/
|
|
|
|
limit = rwb->wb_background;
|
|
|
|
} else
|
|
|
|
limit = rwb->wb_normal;
|
|
|
|
|
|
|
|
return limit;
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline bool may_queue(struct rq_wb *rwb, struct rq_wait *rqw,
|
2017-06-20 13:06:13 +03:00
|
|
|
wait_queue_entry_t *wait, unsigned long rw)
|
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 22:36:15 +03:00
|
|
|
{
|
|
|
|
/*
|
|
|
|
* inc it here even if disabled, since we'll dec it at completion.
|
|
|
|
* this only happens if the task was sleeping in __wbt_wait(),
|
|
|
|
* and someone turned it off at the same time.
|
|
|
|
*/
|
|
|
|
if (!rwb_enabled(rwb)) {
|
|
|
|
atomic_inc(&rqw->inflight);
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* If the waitqueue is already active and we are not the next
|
|
|
|
* in line to be woken up, wait for our turn.
|
|
|
|
*/
|
|
|
|
if (waitqueue_active(&rqw->wait) &&
|
sched/wait: Disambiguate wq_entry->task_list and wq_head->task_list naming
So I've noticed a number of instances where it was not obvious from the
code whether ->task_list was for a wait-queue head or a wait-queue entry.
Furthermore, there's a number of wait-queue users where the lists are
not for 'tasks' but other entities (poll tables, etc.), in which case
the 'task_list' name is actively confusing.
To clear this all up, name the wait-queue head and entry list structure
fields unambiguously:
struct wait_queue_head::task_list => ::head
struct wait_queue_entry::task_list => ::entry
For example, this code:
rqw->wait.task_list.next != &wait->task_list
... is was pretty unclear (to me) what it's doing, while now it's written this way:
rqw->wait.head.next != &wait->entry
... which makes it pretty clear that we are iterating a list until we see the head.
Other examples are:
list_for_each_entry_safe(pos, next, &x->task_list, task_list) {
list_for_each_entry(wq, &fence->wait.task_list, task_list) {
... where it's unclear (to me) what we are iterating, and during review it's
hard to tell whether it's trying to walk a wait-queue entry (which would be
a bug), while now it's written as:
list_for_each_entry_safe(pos, next, &x->head, entry) {
list_for_each_entry(wq, &fence->wait.head, entry) {
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2017-06-20 13:06:46 +03:00
|
|
|
rqw->wait.head.next != &wait->entry)
|
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 22:36:15 +03:00
|
|
|
return false;
|
|
|
|
|
|
|
|
return atomic_inc_below(&rqw->inflight, get_limit(rwb, rw));
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Block if we will exceed our limit, or if we are currently waiting for
|
|
|
|
* the timer to kick off queuing again.
|
|
|
|
*/
|
|
|
|
static void __wbt_wait(struct rq_wb *rwb, unsigned long rw, spinlock_t *lock)
|
2017-01-02 19:48:47 +03:00
|
|
|
__releases(lock)
|
|
|
|
__acquires(lock)
|
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 22:36:15 +03:00
|
|
|
{
|
|
|
|
struct rq_wait *rqw = get_rq_wait(rwb, current_is_kswapd());
|
|
|
|
DEFINE_WAIT(wait);
|
|
|
|
|
|
|
|
if (may_queue(rwb, rqw, &wait, rw))
|
|
|
|
return;
|
|
|
|
|
|
|
|
do {
|
|
|
|
prepare_to_wait_exclusive(&rqw->wait, &wait,
|
|
|
|
TASK_UNINTERRUPTIBLE);
|
|
|
|
|
|
|
|
if (may_queue(rwb, rqw, &wait, rw))
|
|
|
|
break;
|
|
|
|
|
2017-01-02 19:48:47 +03:00
|
|
|
if (lock) {
|
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 22:36:15 +03:00
|
|
|
spin_unlock_irq(lock);
|
2017-01-02 19:48:47 +03:00
|
|
|
io_schedule();
|
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 22:36:15 +03:00
|
|
|
spin_lock_irq(lock);
|
2017-01-02 19:48:47 +03:00
|
|
|
} else
|
|
|
|
io_schedule();
|
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 22:36:15 +03:00
|
|
|
} while (1);
|
|
|
|
|
|
|
|
finish_wait(&rqw->wait, &wait);
|
|
|
|
}
|
|
|
|
|
|
|
|
static inline bool wbt_should_throttle(struct rq_wb *rwb, struct bio *bio)
|
|
|
|
{
|
|
|
|
const int op = bio_op(bio);
|
|
|
|
|
|
|
|
/*
|
2016-12-09 16:19:06 +03:00
|
|
|
* If not a WRITE, do nothing
|
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 22:36:15 +03:00
|
|
|
*/
|
2016-12-09 16:19:06 +03:00
|
|
|
if (op != REQ_OP_WRITE)
|
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 22:36:15 +03:00
|
|
|
return false;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Don't throttle WRITE_ODIRECT
|
|
|
|
*/
|
|
|
|
if ((bio->bi_opf & (REQ_SYNC | REQ_IDLE)) == (REQ_SYNC | REQ_IDLE))
|
|
|
|
return false;
|
|
|
|
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Returns true if the IO request should be accounted, false if not.
|
|
|
|
* May sleep, if we have exceeded the writeback limits. Caller can pass
|
|
|
|
* in an irq held spinlock, if it holds one when calling this function.
|
|
|
|
* If we do sleep, we'll release and re-grab it.
|
|
|
|
*/
|
2017-01-02 19:46:15 +03:00
|
|
|
enum wbt_flags wbt_wait(struct rq_wb *rwb, struct bio *bio, spinlock_t *lock)
|
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 22:36:15 +03:00
|
|
|
{
|
|
|
|
unsigned int ret = 0;
|
|
|
|
|
|
|
|
if (!rwb_enabled(rwb))
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (bio_op(bio) == REQ_OP_READ)
|
|
|
|
ret = WBT_READ;
|
|
|
|
|
|
|
|
if (!wbt_should_throttle(rwb, bio)) {
|
|
|
|
if (ret & WBT_READ)
|
|
|
|
wb_timestamp(rwb, &rwb->last_issue);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
__wbt_wait(rwb, bio->bi_opf, lock);
|
|
|
|
|
blk-stat: convert to callback-based statistics reporting
Currently, statistics are gathered in ~0.13s windows, and users grab the
statistics whenever they need them. This is not ideal for both in-tree
users:
1. Writeback throttling wants its own dynamically sized window of
statistics. Since the blk-stats statistics are reset after every
window and the wbt windows don't line up with the blk-stats windows,
wbt doesn't see every I/O.
2. Polling currently grabs the statistics on every I/O. Again, depending
on how the window lines up, we may miss some I/Os. It's also
unnecessary overhead to get the statistics on every I/O; the hybrid
polling heuristic would be just as happy with the statistics from the
previous full window.
This reworks the blk-stats infrastructure to be callback-based: users
register a callback that they want called at a given time with all of
the statistics from the window during which the callback was active.
Users can dynamically bucketize the statistics. wbt and polling both
currently use read vs. write, but polling can be extended to further
subdivide based on request size.
The callbacks are kept on an RCU list, and each callback has percpu
stats buffers. There will only be a few users, so the overhead on the
I/O completion side is low. The stats flushing is also simplified
considerably: since the timer function is responsible for clearing the
statistics, we don't have to worry about stale statistics.
wbt is a trivial conversion. After the conversion, the windowing problem
mentioned above is fixed.
For polling, we register an extra callback that caches the previous
window's statistics in the struct request_queue for the hybrid polling
heuristic to use.
Since we no longer have a single stats buffer for the request queue,
this also removes the sysfs and debugfs stats entries. To replace those,
we add a debugfs entry for the poll statistics.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
2017-03-21 18:56:08 +03:00
|
|
|
if (!blk_stat_is_active(rwb->cb))
|
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 22:36:15 +03:00
|
|
|
rwb_arm_timer(rwb);
|
|
|
|
|
|
|
|
if (current_is_kswapd())
|
|
|
|
ret |= WBT_KSWAPD;
|
|
|
|
|
|
|
|
return ret | WBT_TRACKED;
|
|
|
|
}
|
|
|
|
|
|
|
|
void wbt_issue(struct rq_wb *rwb, struct blk_issue_stat *stat)
|
|
|
|
{
|
|
|
|
if (!rwb_enabled(rwb))
|
|
|
|
return;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Track sync issue, in case it takes a long time to complete. Allows
|
|
|
|
* us to react quicker, if a sync IO takes a long time to complete.
|
|
|
|
* Note that this is just a hint. 'stat' can go away when the
|
|
|
|
* request completes, so it's important we never dereference it. We
|
|
|
|
* only use the address to compare with, which is why we store the
|
|
|
|
* sync_issue time locally.
|
|
|
|
*/
|
|
|
|
if (wbt_is_read(stat) && !rwb->sync_issue) {
|
|
|
|
rwb->sync_cookie = stat;
|
|
|
|
rwb->sync_issue = blk_stat_time(stat);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void wbt_requeue(struct rq_wb *rwb, struct blk_issue_stat *stat)
|
|
|
|
{
|
|
|
|
if (!rwb_enabled(rwb))
|
|
|
|
return;
|
|
|
|
if (stat == rwb->sync_cookie) {
|
|
|
|
rwb->sync_issue = 0;
|
|
|
|
rwb->sync_cookie = NULL;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void wbt_set_queue_depth(struct rq_wb *rwb, unsigned int depth)
|
|
|
|
{
|
|
|
|
if (rwb) {
|
|
|
|
rwb->queue_depth = depth;
|
|
|
|
wbt_update_limits(rwb);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void wbt_set_write_cache(struct rq_wb *rwb, bool write_cache_on)
|
|
|
|
{
|
|
|
|
if (rwb)
|
|
|
|
rwb->wc = write_cache_on;
|
|
|
|
}
|
|
|
|
|
2017-04-11 12:29:01 +03:00
|
|
|
/*
|
2017-10-09 17:27:21 +03:00
|
|
|
* Disable wbt, if enabled by default.
|
2016-11-28 19:25:50 +03:00
|
|
|
*/
|
|
|
|
void wbt_disable_default(struct request_queue *q)
|
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 22:36:15 +03:00
|
|
|
{
|
2016-11-28 19:25:50 +03:00
|
|
|
struct rq_wb *rwb = q->rq_wb;
|
|
|
|
|
2017-04-11 12:29:01 +03:00
|
|
|
if (rwb && rwb->enable_state == WBT_STATE_ON_DEFAULT)
|
|
|
|
wbt_exit(q);
|
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 22:36:15 +03:00
|
|
|
}
|
2016-11-28 19:25:50 +03:00
|
|
|
EXPORT_SYMBOL_GPL(wbt_disable_default);
|
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 22:36:15 +03:00
|
|
|
|
2017-04-19 12:33:27 +03:00
|
|
|
/*
|
|
|
|
* Enable wbt if defaults are configured that way
|
|
|
|
*/
|
|
|
|
void wbt_enable_default(struct request_queue *q)
|
|
|
|
{
|
|
|
|
/* Throttling already enabled? */
|
|
|
|
if (q->rq_wb)
|
|
|
|
return;
|
|
|
|
|
|
|
|
/* Queue not registered? Maybe shutting down... */
|
|
|
|
if (!test_bit(QUEUE_FLAG_REGISTERED, &q->queue_flags))
|
|
|
|
return;
|
|
|
|
|
|
|
|
if ((q->mq_ops && IS_ENABLED(CONFIG_BLK_WBT_MQ)) ||
|
|
|
|
(q->request_fn && IS_ENABLED(CONFIG_BLK_WBT_SQ)))
|
|
|
|
wbt_init(q);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(wbt_enable_default);
|
|
|
|
|
2016-11-28 19:22:47 +03:00
|
|
|
u64 wbt_default_latency_nsec(struct request_queue *q)
|
|
|
|
{
|
|
|
|
/*
|
|
|
|
* We default to 2msec for non-rotational storage, and 75msec
|
|
|
|
* for rotational storage.
|
|
|
|
*/
|
|
|
|
if (blk_queue_nonrot(q))
|
|
|
|
return 2000000ULL;
|
|
|
|
else
|
|
|
|
return 75000000ULL;
|
|
|
|
}
|
|
|
|
|
2017-04-21 16:55:42 +03:00
|
|
|
static int wbt_data_dir(const struct request *rq)
|
|
|
|
{
|
|
|
|
return rq_data_dir(rq);
|
|
|
|
}
|
|
|
|
|
2016-11-11 07:50:51 +03:00
|
|
|
int wbt_init(struct request_queue *q)
|
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 22:36:15 +03:00
|
|
|
{
|
|
|
|
struct rq_wb *rwb;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
BUILD_BUG_ON(WBT_NR_BITS > BLK_STAT_RES_BITS);
|
|
|
|
|
|
|
|
rwb = kzalloc(sizeof(*rwb), GFP_KERNEL);
|
|
|
|
if (!rwb)
|
|
|
|
return -ENOMEM;
|
|
|
|
|
2017-04-21 16:55:42 +03:00
|
|
|
rwb->cb = blk_stat_alloc_callback(wb_timer_fn, wbt_data_dir, 2, rwb);
|
blk-stat: convert to callback-based statistics reporting
Currently, statistics are gathered in ~0.13s windows, and users grab the
statistics whenever they need them. This is not ideal for both in-tree
users:
1. Writeback throttling wants its own dynamically sized window of
statistics. Since the blk-stats statistics are reset after every
window and the wbt windows don't line up with the blk-stats windows,
wbt doesn't see every I/O.
2. Polling currently grabs the statistics on every I/O. Again, depending
on how the window lines up, we may miss some I/Os. It's also
unnecessary overhead to get the statistics on every I/O; the hybrid
polling heuristic would be just as happy with the statistics from the
previous full window.
This reworks the blk-stats infrastructure to be callback-based: users
register a callback that they want called at a given time with all of
the statistics from the window during which the callback was active.
Users can dynamically bucketize the statistics. wbt and polling both
currently use read vs. write, but polling can be extended to further
subdivide based on request size.
The callbacks are kept on an RCU list, and each callback has percpu
stats buffers. There will only be a few users, so the overhead on the
I/O completion side is low. The stats flushing is also simplified
considerably: since the timer function is responsible for clearing the
statistics, we don't have to worry about stale statistics.
wbt is a trivial conversion. After the conversion, the windowing problem
mentioned above is fixed.
For polling, we register an extra callback that caches the previous
window's statistics in the struct request_queue for the hybrid polling
heuristic to use.
Since we no longer have a single stats buffer for the request queue,
this also removes the sysfs and debugfs stats entries. To replace those,
we add a debugfs entry for the poll statistics.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
2017-03-21 18:56:08 +03:00
|
|
|
if (!rwb->cb) {
|
|
|
|
kfree(rwb);
|
|
|
|
return -ENOMEM;
|
|
|
|
}
|
|
|
|
|
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 22:36:15 +03:00
|
|
|
for (i = 0; i < WBT_NUM_RWQ; i++) {
|
|
|
|
atomic_set(&rwb->rq_wait[i].inflight, 0);
|
|
|
|
init_waitqueue_head(&rwb->rq_wait[i].wait);
|
|
|
|
}
|
|
|
|
|
|
|
|
rwb->last_comp = rwb->last_issue = jiffies;
|
2016-11-11 07:52:53 +03:00
|
|
|
rwb->queue = q;
|
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 22:36:15 +03:00
|
|
|
rwb->win_nsec = RWB_WINDOW_NSEC;
|
2016-11-28 19:40:34 +03:00
|
|
|
rwb->enable_state = WBT_STATE_ON_DEFAULT;
|
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 22:36:15 +03:00
|
|
|
wbt_update_limits(rwb);
|
|
|
|
|
|
|
|
/*
|
blk-stat: convert to callback-based statistics reporting
Currently, statistics are gathered in ~0.13s windows, and users grab the
statistics whenever they need them. This is not ideal for both in-tree
users:
1. Writeback throttling wants its own dynamically sized window of
statistics. Since the blk-stats statistics are reset after every
window and the wbt windows don't line up with the blk-stats windows,
wbt doesn't see every I/O.
2. Polling currently grabs the statistics on every I/O. Again, depending
on how the window lines up, we may miss some I/Os. It's also
unnecessary overhead to get the statistics on every I/O; the hybrid
polling heuristic would be just as happy with the statistics from the
previous full window.
This reworks the blk-stats infrastructure to be callback-based: users
register a callback that they want called at a given time with all of
the statistics from the window during which the callback was active.
Users can dynamically bucketize the statistics. wbt and polling both
currently use read vs. write, but polling can be extended to further
subdivide based on request size.
The callbacks are kept on an RCU list, and each callback has percpu
stats buffers. There will only be a few users, so the overhead on the
I/O completion side is low. The stats flushing is also simplified
considerably: since the timer function is responsible for clearing the
statistics, we don't have to worry about stale statistics.
wbt is a trivial conversion. After the conversion, the windowing problem
mentioned above is fixed.
For polling, we register an extra callback that caches the previous
window's statistics in the struct request_queue for the hybrid polling
heuristic to use.
Since we no longer have a single stats buffer for the request queue,
this also removes the sysfs and debugfs stats entries. To replace those,
we add a debugfs entry for the poll statistics.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
2017-03-21 18:56:08 +03:00
|
|
|
* Assign rwb and add the stats callback.
|
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 22:36:15 +03:00
|
|
|
*/
|
|
|
|
q->rq_wb = rwb;
|
blk-stat: convert to callback-based statistics reporting
Currently, statistics are gathered in ~0.13s windows, and users grab the
statistics whenever they need them. This is not ideal for both in-tree
users:
1. Writeback throttling wants its own dynamically sized window of
statistics. Since the blk-stats statistics are reset after every
window and the wbt windows don't line up with the blk-stats windows,
wbt doesn't see every I/O.
2. Polling currently grabs the statistics on every I/O. Again, depending
on how the window lines up, we may miss some I/Os. It's also
unnecessary overhead to get the statistics on every I/O; the hybrid
polling heuristic would be just as happy with the statistics from the
previous full window.
This reworks the blk-stats infrastructure to be callback-based: users
register a callback that they want called at a given time with all of
the statistics from the window during which the callback was active.
Users can dynamically bucketize the statistics. wbt and polling both
currently use read vs. write, but polling can be extended to further
subdivide based on request size.
The callbacks are kept on an RCU list, and each callback has percpu
stats buffers. There will only be a few users, so the overhead on the
I/O completion side is low. The stats flushing is also simplified
considerably: since the timer function is responsible for clearing the
statistics, we don't have to worry about stale statistics.
wbt is a trivial conversion. After the conversion, the windowing problem
mentioned above is fixed.
For polling, we register an extra callback that caches the previous
window's statistics in the struct request_queue for the hybrid polling
heuristic to use.
Since we no longer have a single stats buffer for the request queue,
this also removes the sysfs and debugfs stats entries. To replace those,
we add a debugfs entry for the poll statistics.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
2017-03-21 18:56:08 +03:00
|
|
|
blk_stat_add_callback(q, rwb->cb);
|
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 22:36:15 +03:00
|
|
|
|
2016-11-28 19:22:47 +03:00
|
|
|
rwb->min_lat_nsec = wbt_default_latency_nsec(q);
|
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 22:36:15 +03:00
|
|
|
|
|
|
|
wbt_set_queue_depth(rwb, blk_queue_depth(q));
|
|
|
|
wbt_set_write_cache(rwb, test_bit(QUEUE_FLAG_WC, &q->queue_flags));
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
void wbt_exit(struct request_queue *q)
|
|
|
|
{
|
|
|
|
struct rq_wb *rwb = q->rq_wb;
|
|
|
|
|
|
|
|
if (rwb) {
|
blk-stat: convert to callback-based statistics reporting
Currently, statistics are gathered in ~0.13s windows, and users grab the
statistics whenever they need them. This is not ideal for both in-tree
users:
1. Writeback throttling wants its own dynamically sized window of
statistics. Since the blk-stats statistics are reset after every
window and the wbt windows don't line up with the blk-stats windows,
wbt doesn't see every I/O.
2. Polling currently grabs the statistics on every I/O. Again, depending
on how the window lines up, we may miss some I/Os. It's also
unnecessary overhead to get the statistics on every I/O; the hybrid
polling heuristic would be just as happy with the statistics from the
previous full window.
This reworks the blk-stats infrastructure to be callback-based: users
register a callback that they want called at a given time with all of
the statistics from the window during which the callback was active.
Users can dynamically bucketize the statistics. wbt and polling both
currently use read vs. write, but polling can be extended to further
subdivide based on request size.
The callbacks are kept on an RCU list, and each callback has percpu
stats buffers. There will only be a few users, so the overhead on the
I/O completion side is low. The stats flushing is also simplified
considerably: since the timer function is responsible for clearing the
statistics, we don't have to worry about stale statistics.
wbt is a trivial conversion. After the conversion, the windowing problem
mentioned above is fixed.
For polling, we register an extra callback that caches the previous
window's statistics in the struct request_queue for the hybrid polling
heuristic to use.
Since we no longer have a single stats buffer for the request queue,
this also removes the sysfs and debugfs stats entries. To replace those,
we add a debugfs entry for the poll statistics.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
2017-03-21 18:56:08 +03:00
|
|
|
blk_stat_remove_callback(q, rwb->cb);
|
|
|
|
blk_stat_free_callback(rwb->cb);
|
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 22:36:15 +03:00
|
|
|
q->rq_wb = NULL;
|
|
|
|
kfree(rwb);
|
|
|
|
}
|
|
|
|
}
|