From: Alan Huang <mmpgouride@gmail.com>
To: paulmck@kernel.org
Cc: perfbook@vger.kernel.org, Alan Huang <mmpgouride@gmail.com>
Subject: [PATCH] together: Fix the description of state traversal
Date: Sun, 28 May 2023 16:40:20 +0000 [thread overview]
Message-ID: <20230528164020.15935-1-mmpgouride@gmail.com> (raw)
There seem to be some issues with the description of state transitions.
This patch fixes that.
Signed-off-by: Alan Huang <mmpgouride@gmail.com>
---
together/applyrcu.tex | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/together/applyrcu.tex b/together/applyrcu.tex
index 09a265f7..dee027b9 100644
--- a/together/applyrcu.tex
+++ b/together/applyrcu.tex
@@ -676,11 +676,12 @@ The normal path through this state machine traverses the states CLOSED,
OPEN, CLOSING (with an invocation of \co{call_rcu()}), and back to CLOSED
once the callback has been invoked.
If \co{open()} is invoked before the grace period completes, the
-state machine traverses the cycle OPEN, CLOSING (with an invocation
-of \co{call_rcu()}), and back to CLOSED once the callback has been invoked.
+state machine traverses the cycle OPEN, CLOSING (with
+an invocation of \co{call_rcu()}), REOPENING, and back to OPEN once the
+callback has been invoked.
If \co{open()} and then \co{close()} are invoked before the grace period
completes, the state machine traverses the cycle OPEN, CLOSING (with
-an invocation of \co{call_rcu()}), REOPENING, and back to OPEN once the
+an invocation of \co{call_rcu()}), REOPENING, RECLOSING, and back to CLOSING once the
callback has been invoked.
Given an indefinite alternating sequence of \co{close()} and \co{open()}
--
2.34.1
next reply other threads:[~2023-05-28 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 16:40 Alan Huang [this message]
2023-05-30 0:40 ` [PATCH] together: Fix the description of state traversal Paul E. McKenney
2023-05-30 15:19 ` Alan Huang
2023-06-02 18:22 ` Paul E. McKenney
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=20230528164020.15935-1-mmpgouride@gmail.com \
--to=mmpgouride@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).