DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
To: olivier.matz@6wind.com, prateekag@cse.iitb.ac.in,
	ferruh.yigit@intel.com, thomas@monjalon.net
Cc: dev@dpdk.org, nd@arm.com,
	Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
Subject: [dpdk-dev] [PATCH v4 1/2] doc/rcu: correct quiescent state description
Date: Wed, 19 Feb 2020 15:05:29 -0600
Message-ID: <20200219210530.22863-1-honnappa.nagarahalli@arm.com> (raw)
In-Reply-To: <20200203045608.5870-1-prateekag@cse.iitb.ac.in>

The quiescent state description refers to an incorrect

Fixes: 64994b56cfd7 ("rcu: add RCU library supporting QSBR mechanism")
Cc: stable@dpdk.org

Signed-off-by: Prateek Agarwal <prateekag@cse.iitb.ac.in>
Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
1) Seperated the commits for ring and RCU changes
2) Changed the commit logs

 doc/guides/prog_guide/rcu_lib.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/guides/prog_guide/rcu_lib.rst b/doc/guides/prog_guide/rcu_lib.rst
index 8d0dfcf29..9b0bf138f 100644
--- a/doc/guides/prog_guide/rcu_lib.rst
+++ b/doc/guides/prog_guide/rcu_lib.rst
@@ -61,7 +61,7 @@ wait till thread 2 enters quiescent state as well.
 However, the writer does not need to wait for reader thread 3 to enter
 quiescent state. Reader thread 3 was not accessing D1 when the delete
-operation happened. So, reader thread 1 will not have a reference to the
+operation happened. So, reader thread 3 will not have a reference to the
 deleted entry.
 It can be noted that, the critical sections for D2 is a quiescent state

  parent reply	other threads:[~2020-02-19 21:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-03  4:56 [dpdk-dev] [PATCH] Documentation errata:RCU_lib.rst and Ring fig 6.10 corrected prateekag
2020-02-16 20:16 ` Thomas Monjalon
2020-02-19 21:05 ` Honnappa Nagarahalli [this message]
2020-02-19 21:05   ` [dpdk-dev] [PATCH v4 2/2] doc/ring: correct multi producer enqueue figure Honnappa Nagarahalli
2020-02-19 23:36     ` Honnappa Nagarahalli
2020-02-19 23:35   ` [dpdk-dev] [PATCH v4 1/2] doc/rcu: correct quiescent state description Honnappa Nagarahalli
2020-02-21 17:31   ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200219210530.22863-1-honnappa.nagarahalli@arm.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=nd@arm.com \
    --cc=olivier.matz@6wind.com \
    --cc=prateekag@cse.iitb.ac.in \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git