2019-06-27 04:07:05 +08:00
|
|
|
.. _rcu_concepts:
|
|
|
|
|
|
|
|
|
|
============
|
|
|
|
|
RCU concepts
|
|
|
|
|
============
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
2019-08-02 05:39:20 +08:00
|
|
|
:maxdepth: 3
|
2019-06-27 04:07:05 +08:00
|
|
|
|
2019-10-29 04:24:17 +08:00
|
|
|
arrayRCU
|
2019-11-07 14:32:41 +08:00
|
|
|
rcubarrier
|
2019-11-02 16:01:07 +08:00
|
|
|
rcu_dereference
|
2019-11-06 21:09:50 +08:00
|
|
|
whatisRCU
|
2019-06-27 04:07:05 +08:00
|
|
|
rcu
|
|
|
|
|
listRCU
|
2019-10-29 05:42:52 +08:00
|
|
|
NMI-RCU
|
2019-06-27 04:07:05 +08:00
|
|
|
UP
|
|
|
|
|
|
docs: rcu: convert some articles from html to ReST
There are 4 RCU articles that are written on html format.
The way they are, they can't be part of the Linux Kernel
documentation body nor share the styles and pdf output.
So, convert them to ReST format.
This way, make htmldocs and make pdfdocs will produce a
documentation output that will be like the original ones, but
will be part of the Linux Kernel documentation body.
Part of the conversion was done with the help of pandoc, but
the result had some broken things that had to be manually
fixed.
Following are manual changes Mauro made when doing the automatic conversion:
Quoting from: https://lore.kernel.org/rcu/20190726154550.5eeae294@coco.lan/
> > At least the pandoc's version I used here has a bug: its conversion
> > from html to ReST on those files only start after a <body> tag - or
> > when the first quiz table starts. I only discovered that adding a
> > <body> at the beginning of the file solve this book at the last
> > conversions.
> >
> > So, for most html->ReST conversions, I manually converted the first
> > part of the document, basically stripping html paragraph tags and
> > by replacing highlights by the ReST syntax.
> >
> > Also, all the quiz tables seem to assume some javascript macro or
> > css style that would be hiding the answer part until the mouse moves
> > to it. Such macro/css was not there at the kernel tree. So, the quiz
> > answers have the same color as the background, making them invisible.
> > Even if we had such macro/css, this is not portable for pdf/LaTeX output
> > (and I'm not sure if this would work with ePub).
> >
> > So, I ended by manually doing the table conversion.
> >
> > Finally, I double-checked if the conversions ended ok, addressing any
> > issues that might have heppened.
> >
> > So, after both automatic conversion and manual fixes, I opened both the
> > html files produced by Sphinx and the original ones and compared them
> > line per line (except for the indexes, as Sphinx produces them
> > automatically), in order to see if all information from the original
> > files will be there on a format close to what we have on other ReST
> > files, fixing any pending issues if any.
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
2019-08-02 05:39:18 +08:00
|
|
|
Design/Memory-Ordering/Tree-RCU-Memory-Ordering
|
|
|
|
|
Design/Expedited-Grace-Periods/Expedited-Grace-Periods
|
|
|
|
|
Design/Requirements/Requirements
|
|
|
|
|
Design/Data-Structures/Data-Structures
|
|
|
|
|
|
2019-06-27 04:07:05 +08:00
|
|
|
.. only:: subproject and html
|
|
|
|
|
|
|
|
|
|
Indices
|
|
|
|
|
=======
|
|
|
|
|
|
|
|
|
|
* :ref:`genindex`
|