public inbox for perfbook@vger.kernel.org
 help / color / mirror / Atom feed
From: Kunwu Chan <kunwu.chan@linux.dev>
To: perfbook@vger.kernel.org
Cc: paulmck@kernel.org, Kunwu Chan <kunwu.chan@linux.dev>
Subject: [PATCH] defer/whichtochoose: Fix incomplete RCU object reference
Date: Tue, 24 Feb 2026 23:17:12 +0800	[thread overview]
Message-ID: <20260224151712.2743076-1-kunwu.chan@linux.dev> (raw)

Replace the incomplete phrase "all other RCU" with the more precise
"all other RCU-deferred objects", clarifying that what gets blocked
from being freed are objects awaiting RCU grace-period reclamation,
not RCU itself.

Signed-off-by: Kunwu Chan <kunwu.chan@linux.dev>
---
 defer/whichtochoose.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/defer/whichtochoose.tex b/defer/whichtochoose.tex
index 139c9636..ff4545bc 100644
--- a/defer/whichtochoose.tex
+++ b/defer/whichtochoose.tex
@@ -118,8 +118,8 @@ The ``Duration of Protection'' row describes constraints (if any) on how
 long a period of time a user may protect a given object.
 Reference counting and hazard pointers can both protect objects for
 extended time periods with no untoward side effects, but
-maintaining an RCU reference to even one object prevents all other RCU
-from being freed.
+maintaining an RCU reference to even one object prevents all other
+RCU-deferred objects from being freed.
 RCU readers must therefore be relatively short in order to avoid running
 the system out of memory, with special-purpose implementations such
 as SRCU, Tasks RCU, and Tasks Trace RCU being exceptions to this rule.
-- 
2.25.1


             reply	other threads:[~2026-02-24 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 15:17 Kunwu Chan [this message]
2026-02-24 18:40 ` [PATCH] defer/whichtochoose: Fix incomplete RCU object reference 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=20260224151712.2743076-1-kunwu.chan@linux.dev \
    --to=kunwu.chan@linux.dev \
    --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