From: Elad Lahav <e2lahav@gmail.com>
To: perfbook@vger.kernel.org
Cc: Elad Lahav <e2lahav@gmail.com>
Subject: [PATCH] RCU fundamentals: too many ares
Date: Fri, 18 Nov 2022 03:23:45 -0500 [thread overview]
Message-ID: <20221118082344.216904-1-e2lahav@gmail.com> (raw)
Signed-off-by: Elad Lahav <e2lahav@gmail.com>
---
defer/rcufundamental.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/defer/rcufundamental.tex b/defer/rcufundamental.tex
index 82d04bba..39b2f7ff 100644
--- a/defer/rcufundamental.tex
+++ b/defer/rcufundamental.tex
@@ -546,7 +546,7 @@ that single-item lookups are much more common in practice than are
full-data-structure traversals.
After all, full-data-structure traversals are much more expensive than
single-item lookups, so developers are motivated to avoid such traversals.
-Not only are concurrent updates are less likely to affect a single-item
+Not only are concurrent updates less likely to affect a single-item
lookup than they are a full traversal, but it is also the case that an
isolated single-item lookup has no way of detecting such inconsistencies.
As a result, in the common case, such inconsistencies are not just
--
2.34.1
next reply other threads:[~2022-11-18 8:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 8:23 Elad Lahav [this message]
2022-11-18 21:38 ` [PATCH] RCU fundamentals: too many ares 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=20221118082344.216904-1-e2lahav@gmail.com \
--to=e2lahav@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.