memorder: Fix two trivial typos
PATCH 1/1 memorder: Fix two trivial typos
--- memorder/memorder.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
memorder/memorder.tex +2 -2
@@ -3125,7 +3125,7 @@ Sections~\ref{sec:toolsoftrade:A Volatile Solution}-\ref{sec:toolsoftrade:Avoidi cause the compiler to discard a previously loaded value from its register, and then reload it later on. Invented loads can be prevented by using \co{READ_ONCE()} or by - enforcing ordering as callout out above between the load and a + enforcing ordering as called out above between the load and a later use of its value using \co{barrier()}. \item Stores can be invented before a plain store, for example, by using the stored-to location as temporary storage.
@@ -3160,7 +3160,7 @@ optimizing your parallel algorithm out of existence. Compilers are starting to provide other mechanisms for avoiding load and store tearing, for example, \co{memory_order_relaxed} atomic loads and stores, however, work is still -needed~/\cite{JonathanCorbet2016C11atomics} +needed~\cite{JonathanCorbet2016C11atomics}. In addition, compiler issues aside, \co{volatile} is still needed to avoid fusing and invention of accesses, including C11 atomic accesses.
Signature · 1 line
2.10.0
PATCH 1/5 toolsoftrade: Polish an ambiguous sentence
A sentence calls a 'signal or interrupt handler' as 'interrupt handler'. This commit modifies the sentence to call it just a handler to minimize any confusion.
--- toolsoftrade/toolsoftrade.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
toolsoftrade/toolsoftrade.tex +2 -2
@@ -2365,8 +2365,8 @@ for other accesses to that same variable: All other code must use \co{READ_ONCE()} and \co{WRITE_ONCE()}. \item A shared variable is only accessed by a given CPU or thread and by a signal or interrupt handler running in that CPU's - or thread's context, and the interrupt handler always restores - the values of any variables that it has written before return. + or thread's context, and the handler always restores the values of any + variables that it has written before return. The handler can use plain loads and stores, as can any code that has prevented the handler from being invoked, that is, code that has blocked signals and/or interrupts.
Signature · 1 line
2.10.0
Re: [PATCH 1/5] toolsoftrade: Polish an ambiguous sentence
Quoted 5 lines · SeongJae Park
A sentence calls a 'signal or interrupt handler' as 'interrupt handler'. This commit modifies the sentence to call it just a handler to minimize any confusion.
Signed-off-by SeongJae Park <[email protected]>
Good eyes!!! All five applied and pushed, thank you!
Thanx, Paul
Quoted 22 lines
--- toolsoftrade/toolsoftrade.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)toolsoftrade/toolsoftrade.tex +2
-2@@ -2365,8 +2365,8 @@ for other accesses to that same variable: All other code must use \co{READ_ONCE()} and \co{WRITE_ONCE()}. \item A shared variable is only accessed by a given CPU or thread and by a signal or interrupt handler running in that CPU's - or thread's context, and the interrupt handler always restores - the values of any variables that it has written before return. + or thread's context, and the handler always restores the values of any + variables that it has written before return. The handler can use plain loads and stores, as can any code that has prevented the handler from being invoked, that is, code that has blocked signals and/or interrupts.Signature · 1 line
2.10.0
PATCH 2/5 defer/rcupai: Fix a typo: _pointer()() -> _pointer()
In reply to SeongJae Park--- defer/rcuapi.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
defer/rcuapi.tex +1 -1
@@ -570,7 +570,7 @@ Again, simply loading these pointers using C-language accesses could result in seeing pre-initialization garbage in the pointed-to data. However, if the pointer is merely to be tested and not dereferenced, this protection is not needed. -In this case, \co{rcu_access_pointer()()} may be used. +In this case, \co{rcu_access_pointer()} may be used. Normally, however, protection is required, and so the \co{rcu_dereference()} primitive ensures that subsequent code dereferencing the pointer will see the effects of initialization code
Signature · 1 line
2.10.0
PATCH 3/5 defer/rcuapi: Consistently use dashes for 'RCU-protected' and 'update-side'
In reply to SeongJae ParkOnly one sentence is not placing a 'dash' between two words: 'RCU protected' and 'update side'. This commit adds dashes for better consistency.
--- defer/rcuapi.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
defer/rcuapi.tex +2 -2
@@ -578,8 +578,8 @@ prior to the corresponding \co{rcu_assign_pointer()}, even on Alpha CPUs. On non-Alpha CPUs, \co{rcu_dereference()} documents which pointer dereferences require RCU protection. -Another situation where protection is not required is when update side code -accesses the RCU protected pointer while holding the update-side lock. +Another situation where protection is not required is when update-side code +accesses the RCU-protected pointer while holding the update-side lock. The \co{rcu_dereference_protected()} API member is provided for this situation. Its first parameter is the RCU-protected pointer, and the second
Signature · 1 line
2.10.0
PATCH 4/5 defer: Fix a typo: processof -> process of
In reply to SeongJae Park--- defer/whichtochoose.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
defer/whichtochoose.tex +1 -1
@@ -119,7 +119,7 @@ operation, which is the case for reference counting, hazard pointers, and sequence locks. In the case of reference counting and hazard pointers, retries are only required if an attempt to acquire a reference to a given object while -that object is in the processof being deleted, a topic covered in more +that object is in the process of being deleted, a topic covered in more detail in the next section. Sequence locking must of course retry its critical section should it run concurrently with any update.
Signature · 1 line
2.10.0
PATCH 5/5 defer: Use 'Go' instead of 'golang'
In reply to SeongJae Park'golang' is an abbreviation for 'Go programming language'. Thus, the term 'golang programming language', which is used in the 'defer' chapter has unnecessary duplication. This patch modifies the sentences to use 'Go' instead of 'golang' in general.
--- defer/whichtochoose.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
defer/whichtochoose.tex +2 -2
@@ -493,9 +493,9 @@ QSBR and epoch-based reclamation both of which are types of implementations of RCU. Sheth et al.~\cite{HarshalSheth2016goRCU} -demonstrated the value of leveraging golang's garbage +demonstrated the value of leveraging Go's garbage collector to provide RCU-like functionality, and -the golang programming language provides a \co{Value} type that can +the Go programming language provides a \co{Value} type that can provide this functionality.\footnote{ See \url{https://golang.org/pkg/sync/atomic/\#Value}, particularly the ``Example (ReadMostly)''.}
Signature · 1 line
2.10.0