Skip to contentSkip to conversation

RCU fundamentals: too many ares

PATCH In review Elad Lahav 2 participants 2 messages Nov 18, 2022

lore
Share & tools
lore

Elad Lahav

author
#0 lore raw

PATCH 1/1 RCU fundamentals: too many ares

---
 defer/rcufundamental.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
defer/rcufundamental.tex +1 -1
index 82d04bba..39b2f7ff 100644
@@ -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
Signature · 1 line
2.34.1
#1 lore raw
Quoted 1 line · Elad Lahav

Good catch! Queued and pushed, thank you!

Thanx, Paul

Quoted 20 lines
---
 defer/rcufundamental.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
defer/rcufundamental.tex +1 -1
index 82d04bba..39b2f7ff 100644
@@ -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
Signature · 1 line
2.34.1