summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab+samsung@kernel.org>2019-07-09 17:36:09 +0200
committerMauro Carvalho Chehab <mchehab+samsung@kernel.org>2019-07-15 16:03:04 +0200
commit8bb0776b8b27d548c7e65828ec3a02cb31fe3eed (patch)
tree0528d65c933e3cbf55982cf6a4e60ffc3afdce94
parentdocs: arm: fix a breakage with pdf output (diff)
downloadlinux-8bb0776b8b27d548c7e65828ec3a02cb31fe3eed.tar.xz
linux-8bb0776b8b27d548c7e65828ec3a02cb31fe3eed.zip
docs: block: fix pdf output
Add an extra blank line and use a markup for the enumberated list, in order to make it possible to build the block book on pdf format. Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
-rw-r--r--Documentation/block/biodoc.rst9
1 files changed, 5 insertions, 4 deletions
diff --git a/Documentation/block/biodoc.rst b/Documentation/block/biodoc.rst
index d6e30b680405..c8eb28401332 100644
--- a/Documentation/block/biodoc.rst
+++ b/Documentation/block/biodoc.rst
@@ -9,6 +9,7 @@ Notes on the Generic Block Layer Rewrite in Linux 2.5
here might still be useful.
Notes Written on Jan 15, 2002:
+
- Jens Axboe <jens.axboe@oracle.com>
- Suparna Bhattacharya <suparna@in.ibm.com>
@@ -172,8 +173,8 @@ Some new queue property settings:
New queue flags:
- QUEUE_FLAG_CLUSTER (see 3.2.2)
- QUEUE_FLAG_QUEUED (see 3.2.4)
+ - QUEUE_FLAG_CLUSTER (see 3.2.2)
+ - QUEUE_FLAG_QUEUED (see 3.2.4)
ii. High-mem i/o capabilities are now considered the default
@@ -478,7 +479,7 @@ With this multipage bio design:
- Splitting of an i/o request across multiple devices (as in the case of
lvm or raid) is achieved by cloning the bio (where the clone points to
the same bi_io_vec array, but with the index and size accordingly modified)
-- A linked list of bios is used as before for unrelated merges [*]_ - this
+- A linked list of bios is used as before for unrelated merges [#]_ - this
avoids reallocs and makes independent completions easier to handle.
- Code that traverses the req list can find all the segments of a bio
by using rq_for_each_segment. This handles the fact that a request
@@ -489,7 +490,7 @@ With this multipage bio design:
[TBD: Should preferably also have a bi_voffset and bi_vlen to avoid modifying
bi_offset an len fields]
-.. [*]
+.. [#]
unrelated merges -- a request ends up containing two or more bios that
didn't originate from the same place.