Skip to contentSkip to conversation

glossary: Tweak indexing macro

PATCH Applied Akira Yokosawa 2 participants 2 messages Jan 20, 2022

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 glossary: Tweak indexing macro

Fix some of indexing tags so that they can co-exist with existing index items.

Fixes 4e91046e35c9 ("glossary: Additions from index, A-E")
---
 glossary.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
glossary.tex +3 -3
index 6c1c71e1..84472a9b 100644
@@ -9,7 +9,7 @@
 	        David~Levary~et~al.}}
 
 \begin{description}
-\item[\IXG{Amdahl's Law}:]
+\item[\IXGr{Amdahl's Law}:]
 	If sufficient numbers of CPUs are used to run a job that has both
 	a sequential portion and a concurrent portion, performance and
 	scalability will be limited by the overhead of the sequential
@@ -228,7 +228,7 @@
 	increase the overall cost of the computation, resulting in
 	linear speedups as threads are added (assuming sufficient
 	CPUs are available).
-\item[\IXG{Energy Efficiency}:]
+\item[\IXGalth{Energy Efficiency}{energy}{efficiency}:]
 	Shorthand for ``energy-efficienct use'' in which the goal is to
 	carry out a given computation with reduced energy consumption.
 	Sublinear scalabilty can be an obstacle to energy-efficient use
@@ -510,7 +510,7 @@
 	to store to that pointer.
 	More information is provided in
 	\cref{sec:memorder:Address- and Data-Dependency Difficulties}.
-\item[\IXGh{RCU Read-Side}{Critical Section}:] % @@@ Need all-caps RCU in index!
+\item[\IXGalthmr{RCU Read-Side Critical Section}{RCU read-side}{critical section}:]
 	A section of code protected by RCU, for example, beginning with
 	\co{rcu_read_lock()} and ending with \co{rcu_read_unlock()}.
 	(See ``Read-side critical section''.)

base-commit: 6abfa973f401e7b1fb696ba078376bce77126a4b

Signature · 1 line
2.17.1
#1 lore raw
Quoted 5 lines · Akira Yokosawa

Fix some of indexing tags so that they can co-exist with existing index items.

Fixes 4e91046e35c9 ("glossary: Additions from index, A-E")

And it would appear that you answered my question before I got around to asking it. ;-)

Queued and pushed, thank you very much!

Thanx, Paul

Quoted 40 lines
---
 glossary.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
glossary.tex +3 -3
index 6c1c71e1..84472a9b 100644
@@ -9,7 +9,7 @@
 	        David~Levary~et~al.}}
 
 \begin{description}
-\item[\IXG{Amdahl's Law}:]
+\item[\IXGr{Amdahl's Law}:]
 	If sufficient numbers of CPUs are used to run a job that has both
 	a sequential portion and a concurrent portion, performance and
 	scalability will be limited by the overhead of the sequential
@@ -228,7 +228,7 @@
 	increase the overall cost of the computation, resulting in
 	linear speedups as threads are added (assuming sufficient
 	CPUs are available).
-\item[\IXG{Energy Efficiency}:]
+\item[\IXGalth{Energy Efficiency}{energy}{efficiency}:]
 	Shorthand for ``energy-efficienct use'' in which the goal is to
 	carry out a given computation with reduced energy consumption.
 	Sublinear scalabilty can be an obstacle to energy-efficient use
@@ -510,7 +510,7 @@
 	to store to that pointer.
 	More information is provided in
 	\cref{sec:memorder:Address- and Data-Dependency Difficulties}.
-\item[\IXGh{RCU Read-Side}{Critical Section}:] % @@@ Need all-caps RCU in index!
+\item[\IXGalthmr{RCU Read-Side Critical Section}{RCU read-side}{critical section}:]
 	A section of code protected by RCU, for example, beginning with
 	\co{rcu_read_lock()} and ending with \co{rcu_read_unlock()}.
 	(See ``Read-side critical section''.)

base-commit: 6abfa973f401e7b1fb696ba078376bce77126a4b

Signature · 1 line
2.17.1