[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 3/5] rcu: do not mention atomic_mb_read/set in documentation
From: |
Paolo Bonzini |
Subject: |
[PATCH 3/5] rcu: do not mention atomic_mb_read/set in documentation |
Date: |
Tue, 7 Apr 2020 10:07:44 -0400 |
Signed-off-by: Paolo Bonzini <address@hidden>
---
docs/devel/rcu.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/devel/rcu.txt b/docs/devel/rcu.txt
index d83fed2f79..0ce15ba198 100644
--- a/docs/devel/rcu.txt
+++ b/docs/devel/rcu.txt
@@ -132,7 +132,7 @@ The core RCU API is small:
typeof(*p) atomic_rcu_read(p);
- atomic_rcu_read() is similar to atomic_mb_read(), but it makes
+ atomic_rcu_read() is similar to atomic_load_acquire(), but it makes
some assumptions on the code that calls it. This allows a more
optimized implementation.
@@ -154,7 +154,7 @@ The core RCU API is small:
void atomic_rcu_set(p, typeof(*p) v);
- atomic_rcu_set() is also similar to atomic_mb_set(), and it also
+ atomic_rcu_set() is similar to atomic_store_release(), though it also
makes assumptions on the code that calls it in order to allow a more
optimized implementation.
--
2.18.2
- Re: [PATCH 4/4] async: use explicit memory barriers and relaxed accesses, (continued)
- [PATCH 2/4] atomics: update documentation for C11, Paolo Bonzini, 2020/04/06
- [PATCH 1/4] atomics: convert to reStructuredText, Paolo Bonzini, 2020/04/06
- Re: [RFC PATCH 0/4] async: fix hangs on weakly-ordered architectures, Stefan Hajnoczi, 2020/04/07
- [RFC PATCH 0/4] async: fix hangs on weakly-ordered architectures, Paolo Bonzini, 2020/04/07
- [PATCH 1/5] atomics: convert to reStructuredText, Paolo Bonzini, 2020/04/07
- [PATCH 5/5] async: use explicit memory barriers, Paolo Bonzini, 2020/04/07
- Re: [RFC PATCH 0/4] async: fix hangs on weakly-ordered architectures, Ying Fang, 2020/04/08