* [PATCH -perfbook] future/htm: Fix typo (missing '\' of \IXalt) @ 2021-07-02 9:49 Akira Yokosawa 2021-07-02 11:08 ` [PATCH -perfbook v2] future/htm, summary: Fix typos (missing '\' in indexing macros) Akira Yokosawa 0 siblings, 1 reply; 3+ messages in thread From: Akira Yokosawa @ 2021-07-02 9:49 UTC (permalink / raw) To: Paul E. McKenney; +Cc: perfbook, Akira Yokosawa Fixes: de25a117a9c6 ("index: Add index and acronym tags, take one") Signed-off-by: Akira Yokosawa <akiyks@gmail.com> --- Hi Paul, I fat-fingered this one in the big patch. I'm thinking of adding some rules in the check script to catch this sort of typo. Thanks, Akira -- future/htm.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/future/htm.tex b/future/htm.tex index dc67ba23..7bff0f99 100644 --- a/future/htm.tex +++ b/future/htm.tex @@ -252,7 +252,7 @@ write~\cite{RaviRajwar2012TSX}. schemes~\cite{CScottAnanian2006,KevinEMoore2006} use DRAM as an extremely large victim cache, but integrating such schemes into a production-quality -IXalt{cache-coherence}{cache coherence} mechanism is still an unsolved +\IXalt{cache-coherence}{cache coherence} mechanism is still an unsolved problem. In addition, use of DRAM as a victim cache may have unfortunate performance and energy-efficiency consequences, particularly -- 2.17.1 ^ permalink raw reply related [flat|nested] 3+ messages in thread
* [PATCH -perfbook v2] future/htm, summary: Fix typos (missing '\' in indexing macros) 2021-07-02 9:49 [PATCH -perfbook] future/htm: Fix typo (missing '\' of \IXalt) Akira Yokosawa @ 2021-07-02 11:08 ` Akira Yokosawa 2021-07-04 15:51 ` Paul E. McKenney 0 siblings, 1 reply; 3+ messages in thread From: Akira Yokosawa @ 2021-07-02 11:08 UTC (permalink / raw) To: Paul E. McKenney; +Cc: perfbook, Akira Yokosawa Fixes: b97d9921b0fd ("acronym: future/htm: Tag TM, HTM, STM, and RCU via acronym dictionary") Fixes: de25a117a9c6 ("index: Add index and acronym tags, take one") Signed-off-by: Akira Yokosawa <akiyks@gmail.com> --- Hi again, I said: > I'm thinking of adding some rules in the check script to catch > this sort of typo. , and a tentative script caught two other typos. This v2 patch fixes three typos at once. Updated check script will be posted later along with other punctuation convention fixes. Thanks, Akira -- future/htm.tex | 4 ++-- summary.tex | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/future/htm.tex b/future/htm.tex index dc67ba23..7458f436 100644 --- a/future/htm.tex +++ b/future/htm.tex @@ -150,7 +150,7 @@ HTM is therefore a very real possibility for large non-partitionable data structures, at least assuming relatively small updates. \QuickQuiz{ - Why are relatively small updates important to IXacr{htm} performance + Why are relatively small updates important to \IXacr{htm} performance and scalability? }\QuickQuizAnswer{ The larger the updates, the greater the probability of conflict, @@ -252,7 +252,7 @@ write~\cite{RaviRajwar2012TSX}. schemes~\cite{CScottAnanian2006,KevinEMoore2006} use DRAM as an extremely large victim cache, but integrating such schemes into a production-quality -IXalt{cache-coherence}{cache coherence} mechanism is still an unsolved +\IXalt{cache-coherence}{cache coherence} mechanism is still an unsolved problem. In addition, use of DRAM as a victim cache may have unfortunate performance and energy-efficiency consequences, particularly diff --git a/summary.tex b/summary.tex index 63187998..2ed43920 100644 --- a/summary.tex +++ b/summary.tex @@ -86,7 +86,7 @@ And that goes at least double for concurrent code. where combining concurrency mechanisms with each other or with other design tricks can greatly ease parallel programmers' lives. \Cref{sec:advsync:Advanced Synchronization} looked at advanced -synchronization methods, including lockless programming, IXacrl{nbs}, +synchronization methods, including lockless programming, \IXacrl{nbs}, and parallel real-time computing. \Cref{chp:Advanced Synchronization: Memory Ordering} dug into the critically important topic of memory ordering, presenting techniques -- 2.17.1 ^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH -perfbook v2] future/htm, summary: Fix typos (missing '\' in indexing macros) 2021-07-02 11:08 ` [PATCH -perfbook v2] future/htm, summary: Fix typos (missing '\' in indexing macros) Akira Yokosawa @ 2021-07-04 15:51 ` Paul E. McKenney 0 siblings, 0 replies; 3+ messages in thread From: Paul E. McKenney @ 2021-07-04 15:51 UTC (permalink / raw) To: Akira Yokosawa; +Cc: perfbook On Fri, Jul 02, 2021 at 08:08:26PM +0900, Akira Yokosawa wrote: > Fixes: b97d9921b0fd ("acronym: future/htm: Tag TM, HTM, STM, and RCU via acronym dictionary") > Fixes: de25a117a9c6 ("index: Add index and acronym tags, take one") > Signed-off-by: Akira Yokosawa <akiyks@gmail.com> > --- > Hi again, > > I said: > > > I'm thinking of adding some rules in the check script to catch > > this sort of typo. > > , and a tentative script caught two other typos. > > This v2 patch fixes three typos at once. > > Updated check script will be posted later along with other punctuation > convention fixes. Queued and pushed, thank you! Thanx, Paul > Thanks, Akira > -- > future/htm.tex | 4 ++-- > summary.tex | 2 +- > 2 files changed, 3 insertions(+), 3 deletions(-) > > diff --git a/future/htm.tex b/future/htm.tex > index dc67ba23..7458f436 100644 > --- a/future/htm.tex > +++ b/future/htm.tex > @@ -150,7 +150,7 @@ HTM is therefore a very real possibility for large non-partitionable > data structures, at least assuming relatively small updates. > > \QuickQuiz{ > - Why are relatively small updates important to IXacr{htm} performance > + Why are relatively small updates important to \IXacr{htm} performance > and scalability? > }\QuickQuizAnswer{ > The larger the updates, the greater the probability of conflict, > @@ -252,7 +252,7 @@ write~\cite{RaviRajwar2012TSX}. > schemes~\cite{CScottAnanian2006,KevinEMoore2006} > use DRAM as an extremely large victim cache, but integrating such schemes > into a production-quality > -IXalt{cache-coherence}{cache coherence} mechanism is still an unsolved > +\IXalt{cache-coherence}{cache coherence} mechanism is still an unsolved > problem. > In addition, use of DRAM as a victim cache may have unfortunate > performance and energy-efficiency consequences, particularly > diff --git a/summary.tex b/summary.tex > index 63187998..2ed43920 100644 > --- a/summary.tex > +++ b/summary.tex > @@ -86,7 +86,7 @@ And that goes at least double for concurrent code. > where combining concurrency mechanisms with each other or with other > design tricks can greatly ease parallel programmers' lives. > \Cref{sec:advsync:Advanced Synchronization} looked at advanced > -synchronization methods, including lockless programming, IXacrl{nbs}, > +synchronization methods, including lockless programming, \IXacrl{nbs}, > and parallel real-time computing. > \Cref{chp:Advanced Synchronization: Memory Ordering} dug into the > critically important topic of memory ordering, presenting techniques > -- > 2.17.1 > > ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-07-04 15:54 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-07-02 9:49 [PATCH -perfbook] future/htm: Fix typo (missing '\' of \IXalt) Akira Yokosawa 2021-07-02 11:08 ` [PATCH -perfbook v2] future/htm, summary: Fix typos (missing '\' in indexing macros) Akira Yokosawa 2021-07-04 15:51 ` Paul E. McKenney
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.