From: Josh Triplett <josh@joshtriplett.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
jiangshanlai@gmail.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org,
dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com,
fweisbec@gmail.com, oleg@redhat.com, bobby.prani@gmail.com
Subject: Re: [PATCH tip/core/rcu 1/8] documentation: Record RCU requirements
Date: Fri, 4 Dec 2015 16:07:19 -0800 [thread overview]
Message-ID: <20151205000719.GB26663@cloud> (raw)
In-Reply-To: <1449273026-23633-1-git-send-email-paulmck@linux.vnet.ibm.com>
On Fri, Dec 04, 2015 at 03:50:19PM -0800, Paul E. McKenney wrote:
> This commit adds RCU requirements as published in a 2015 LWN series.
> Bringing these requirements in-tree allows them to be updated as changes
> are discovered.
>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> ---
> .../RCU/Design/Requirements/2013-08-is-it-dead.png | Bin 0 -> 100825 bytes
> .../Design/Requirements/GPpartitionReaders1.svg | 374 +++
> .../RCU/Design/Requirements/RCUApplicability.svg | 237 ++
> .../Design/Requirements/ReadersPartitionGP1.svg | 639 +++++
> .../RCU/Design/Requirements/Requirements.html | 2799 ++++++++++++++++++++
> .../RCU/Design/Requirements/Requirements.htmlx | 2643 ++++++++++++++++++
> Documentation/RCU/Design/htmlqqz.sh | 108 +
> 7 files changed, 6800 insertions(+)
> create mode 100644 Documentation/RCU/Design/Requirements/2013-08-is-it-dead.png
> create mode 100644 Documentation/RCU/Design/Requirements/GPpartitionReaders1.svg
> create mode 100644 Documentation/RCU/Design/Requirements/RCUApplicability.svg
> create mode 100644 Documentation/RCU/Design/Requirements/ReadersPartitionGP1.svg
> create mode 100644 Documentation/RCU/Design/Requirements/Requirements.html
> create mode 100644 Documentation/RCU/Design/Requirements/Requirements.htmlx
If Requirements.html is machine-generated and shouldn't be hand-edited,
and it can be generated without any special tools, then I don't think it
should be committed in the tree; I'd suggest putting it in .gitignore
and generating it from one of the various "make docs" invocations.
Alternatively, if you want to make sure a usable version is in-tree, you
could make the script reversible (easy enough to do if the compiled
version includes some marker comments or similar), and then tell people
to run it in reverse mode, edit, and run it in forward mode. Then you
don't need the .htmlx file at all. :)
next prev parent reply other threads:[~2015-12-05 0:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 23:49 [PATCH tip/core/rcu 0/8] Documentation updates for 4.5 Paul E. McKenney
2015-12-04 23:50 ` [PATCH tip/core/rcu 1/8] documentation: Record RCU requirements Paul E. McKenney
2015-12-05 0:07 ` Josh Triplett [this message]
2015-12-05 0:33 ` Paul E. McKenney
2015-12-05 0:38 ` Josh Triplett
2015-12-05 1:56 ` Paul E. McKenney
2015-12-05 21:19 ` Paul E. McKenney
2015-12-05 0:34 ` Josh Triplett
2015-12-05 1:54 ` Paul E. McKenney
2015-12-05 20:19 ` Paul E. McKenney
2015-12-04 23:50 ` [PATCH tip/core/rcu 2/8] Documentation: Record bottom-bit-zero guarantee for ->next Paul E. McKenney
2015-12-04 23:50 ` [PATCH tip/core/rcu 3/8] documentation: Cover requirements controlling stall warnings Paul E. McKenney
2015-12-04 23:50 ` [PATCH tip/core/rcu 4/8] documentation: Composability analogies Paul E. McKenney
2015-12-04 23:50 ` [PATCH tip/core/rcu 5/8] documentation: Expand on scheduler/RCU deadlock requirements Paul E. McKenney
2015-12-04 23:50 ` [PATCH tip/core/rcu 6/8] documentation: Clarify RCU memory barriers and requirements Paul E. McKenney
2015-12-04 23:50 ` [PATCH tip/core/rcu 7/8] documentation: Update RCU requirements based on expedited changes Paul E. McKenney
2015-12-04 23:50 ` [PATCH tip/core/rcu 8/8] Documentation/memory-barriers.txt: Fix ACCESS_ONCE thinko Paul E. McKenney
2015-12-05 0:42 ` [PATCH tip/core/rcu 0/8] Documentation updates for 4.5 Josh Triplett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151205000719.GB26663@cloud \
--to=josh@joshtriplett.org \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox