diff options
author | Omar Sandoval <osandov@fb.com> | 2017-04-14 01:00:02 -0700 |
---|---|---|
committer | Jens Axboe <axboe@fb.com> | 2017-04-14 14:06:58 -0600 |
commit | 00e043936e9a1c274c29366c7ecd9e17c79418e6 (patch) | |
tree | 600ca18eb94cb522b65f01381ec20c9565508c02 /scripts/package | |
parent | c05f8525f67b7d6489b0502211d4ed35622d9beb (diff) | |
download | linux-00e043936e9a1c274c29366c7ecd9e17c79418e6.tar.bz2 |
blk-mq: introduce Kyber multiqueue I/O scheduler
The Kyber I/O scheduler is an I/O scheduler for fast devices designed to
scale to multiple queues. Users configure only two knobs, the target
read and synchronous write latencies, and the scheduler tunes itself to
achieve that latency goal.
The implementation is based on "tokens", built on top of the scalable
bitmap library. Tokens serve as a mechanism for limiting requests. There
are two tiers of tokens: queueing tokens and dispatch tokens.
A queueing token is required to allocate a request. In fact, these
tokens are actually the blk-mq internal scheduler tags, but the
scheduler manages the allocation directly in order to implement its
policy.
Dispatch tokens are device-wide and split up into two scheduling
domains: reads vs. writes. Each hardware queue dispatches batches
round-robin between the scheduling domains as long as tokens are
available for that domain.
These tokens can be used as the mechanism to enable various policies.
The policy Kyber uses is inspired by active queue management techniques
for network routing, similar to blk-wbt. The scheduler monitors
latencies and scales the number of dispatch tokens accordingly. Queueing
tokens are used to prevent starvation of synchronous requests by
asynchronous requests.
Various extensions are possible, including better heuristics and ionice
support. The new scheduler isn't set as the default yet.
Signed-off-by: Omar Sandoval <osandov@fb.com>
Signed-off-by: Jens Axboe <axboe@fb.com>
Diffstat (limited to 'scripts/package')
0 files changed, 0 insertions, 0 deletions