RCU fundamentals: too many ares
PATCH 1/1 RCU fundamentals: too many ares
Signed-off-by Elad Lahav <[email protected]>
--- defer/rcufundamental.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
defer/rcufundamental.tex +1 -1
@@ -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
Quoted 1 line · Elad Lahav
Signed-off-by Elad Lahav <[email protected]>
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@@ -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 justSignature · 1 line
2.34.1