Convert external links to block layer docs to use internal linking. Signed-off-by: Bagas Sanjaya <bagasdo...@gmail.com> --- Documentation/block/blk-mq.rst | 23 +++++++++++------------ 1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/Documentation/block/blk-mq.rst b/Documentation/block/blk-mq.rst index fc06761b6ea906..4d511feda39cfd 100644 --- a/Documentation/block/blk-mq.rst +++ b/Documentation/block/blk-mq.rst @@ -87,17 +87,16 @@ IO Schedulers There are several schedulers implemented by the block layer, each one following a heuristic to improve the IO performance. They are "pluggable" (as in plug and play), in the sense of they can be selected at run time using sysfs. You -can read more about Linux's IO schedulers `here -<https://www.kernel.org/doc/html/latest/block/index.html>`_. The scheduling -happens only between requests in the same queue, so it is not possible to merge -requests from different queues, otherwise there would be cache trashing and a -need to have a lock for each queue. After the scheduling, the requests are -eligible to be sent to the hardware. One of the possible schedulers to be -selected is the NONE scheduler, the most straightforward one. It will just -place requests on whatever software queue the process is running on, without -any reordering. When the device starts processing requests in the hardware -queue (a.k.a. run the hardware queue), the software queues mapped to that -hardware queue will be drained in sequence according to their mapping. +can read more about Linux's IO schedulers at Documentation/block/index.rst. +The scheduling happens only between requests in the same queue, so it is not +possible to merge requests from different queues, otherwise there would be +cache trashing and a need to have a lock for each queue. After the scheduling, +the requests are eligible to be sent to the hardware. One of the possible +schedulers to be selected is the NONE scheduler, the most straightforward one. +It will just place requests on whatever software queue the process is running +on, without any reordering. When the device starts processing requests in the +hardware queue (a.k.a. run the hardware queue), the software queues mapped to +that hardware queue will be drained in sequence according to their mapping. Hardware dispatch queues ~~~~~~~~~~~~~~~~~~~~~~~~ @@ -143,7 +142,7 @@ Further reading - `NOOP scheduler <https://en.wikipedia.org/wiki/Noop_scheduler>`_ -- `Null block device driver <https://www.kernel.org/doc/html/latest/block/null_blk.html>`_ +- Documentation/block/null_blk.rst Source code documentation ========================= -- An old man doll... just what I always wanted! - Clara
