| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20250829075524.45635-6-bagasdotme@gmail.com> Date: Fri, 29 Aug 2025 14:55:15 +0700 From: Bagas Sanjaya <bagasdotme@...il.com> To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Documentation <linux-doc@...r.kernel.org>, Linux DAMON <damon@...ts.linux.dev>, Linux Memory Management List <linux-mm@...ck.org>, Linux Power Management <linux-pm@...r.kernel.org>, Linux Block Devices <linux-block@...r.kernel.org>, Linux BPF <bpf@...r.kernel.org>, Linux Kernel Workflows <workflows@...r.kernel.org>, Linux KASAN <kasan-dev@...glegroups.com>, Linux Devicetree <devicetree@...r.kernel.org>, Linux fsverity <fsverity@...ts.linux.dev>, Linux MTD <linux-mtd@...ts.infradead.org>, Linux DRI Development <dri-devel@...ts.freedesktop.org>, Linux Kernel Build System <linux-lbuild@...r.kernel.org>, Linux Networking <netdev@...r.kernel.org>, Linux Sound <linux-sound@...r.kernel.org> Cc: Thomas Gleixner <tglx@...utronix.de>, Borislav Petkov <bp@...en8.de>, Peter Zijlstra <peterz@...radead.org>, Josh Poimboeuf <jpoimboe@...nel.org>, Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>, Jonathan Corbet <corbet@....net>, SeongJae Park <sj@...nel.org>, Andrew Morton <akpm@...ux-foundation.org>, David Hildenbrand <david@...hat.com>, Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, "Liam R. Howlett" <Liam.Howlett@...cle.com>, Vlastimil Babka <vbabka@...e.cz>, Mike Rapoport <rppt@...nel.org>, Suren Baghdasaryan <surenb@...gle.com>, Michal Hocko <mhocko@...e.com>, Huang Rui <ray.huang@....com>, "Gautham R. Shenoy" <gautham.shenoy@....com>, Mario Limonciello <mario.limonciello@....com>, Perry Yuan <perry.yuan@....com>, Jens Axboe <axboe@...nel.dk>, Alexei Starovoitov <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, Andrii Nakryiko <andrii@...nel.org>, Martin KaFai Lau <martin.lau@...ux.dev>, Eduard Zingerman <eddyz87@...il.com>, Song Liu <song@...nel.org>, Yonghong Song <yonghong.song@...ux.dev>, John Fastabend <john.fastabend@...il.com>, KP Singh <kpsingh@...nel.org>, Stanislav Fomichev <sdf@...ichev.me>, Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>, Dwaipayan Ray <dwaipayanray1@...il.com>, Lukas Bulwahn <lukas.bulwahn@...il.com>, Joe Perches <joe@...ches.com>, Andrey Ryabinin <ryabinin.a.a@...il.com>, Alexander Potapenko <glider@...gle.com>, Andrey Konovalov <andreyknvl@...il.com>, Dmitry Vyukov <dvyukov@...gle.com>, Vincenzo Frascino <vincenzo.frascino@....com>, Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, Eric Biggers <ebiggers@...nel.org>, tytso@....edu, Richard Weinberger <richard@....at>, Zhihao Cheng <chengzhihao1@...wei.com>, David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>, Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>, Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nicolas.schier@...ux.dev>, Ingo Molnar <mingo@...hat.com>, Will Deacon <will@...nel.org>, Boqun Feng <boqun.feng@...il.com>, Waiman Long <longman@...hat.com>, "David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>, Shay Agroskin <shayagr@...zon.com>, Arthur Kiyanovski <akiyano@...zon.com>, David Arinzon <darinzon@...zon.com>, Saeed Bishara <saeedb@...zon.com>, Andrew Lunn <andrew@...n.ch>, Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>, Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, Alexandru Ciobotaru <alcioa@...zon.com>, The AWS Nitro Enclaves Team <aws-nitro-enclaves-devel@...zon.com>, Jesper Dangaard Brouer <hawk@...nel.org>, Bagas Sanjaya <bagasdotme@...il.com>, Laurent Pinchart <laurent.pinchart@...asonboard.com>, Steve French <stfrench@...rosoft.com>, Meetakshi Setiya <msetiya@...rosoft.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, "Martin K. Petersen" <martin.petersen@...cle.com>, Bart Van Assche <bvanassche@....org>, Thomas Weißschuh <linux@...ssschuh.net>, Masahiro Yamada <masahiroy@...nel.org> Subject: [PATCH 05/14] Documentation: blk-mq: Convert block layer docs external links Convert external links to block layer docs to use internal linking. Signed-off-by: Bagas Sanjaya <bagasdotme@...il.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
Powered by blists - more mailing lists