Subject: [PATCH -perfbook 2/2] advsync: Add narrow space in front of percent 
sign

For consistency, as described in Appendix D.2.1.4.

Signed-off-by: Akira Yokosawa <[email protected]>
---
Hi Paul,

I think it would be helpful to have a macro for this pattern,
say, \pct, which can be used instead, such as:

+       latency $T$, then a 50\pct\ idle system will have latency $2 T$, a
+       10\pct\ idle (90\pct\ utilized) system will have latency $10 T$, a 
1\pct\
+       idle system (99\pct\ utilized) will have latency $100 T$, and so on.

Or, make it a macro \pct{} that can be used as:

+       latency $T$, then a \pct{50}\ idle system will have latency $2 T$, a
+       \pct{10}\ idle (\pct{90}\ utilized) system will have latency $10 T$, a 
\pct{1}\
+       idle system (\pct{99}\ utilized) will have latency $100 T$, and so on.

, or similar.

In case you are wondering, the trailing "\" in "50\pct\" or "\pct{50}\"
is needed to have a (normal width) space after it in the resulting document.
This is the same as those custom macros such as \Power{}, \ARM{}, etc.

Do you have any preference between 50\pct\ and \pct{50}\ ?

        Thanks, Akira
--
 advsync/advsync.tex | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/advsync/advsync.tex b/advsync/advsync.tex
index 7342e323..31731f61 100644
--- a/advsync/advsync.tex
+++ b/advsync/advsync.tex
@@ -458,11 +458,11 @@ largely orthogonal to those that form the basis of 
real-time programming:
        As a rough rule of thumb, latency increases as the reciprocal
        of the idle time.
        In other words, if a nearly idle system has
-       latency $T$, then a 50\% idle system will have latency $2 T$, a
-       10\% idle (90\% utilized) system will have latency $10 T$, a 1\%
-       idle system (99\% utilized) will have latency $100 T$, and so on.
+       latency $T$, then a 50\,\% idle system will have latency $2 T$, a
+       10\,\% idle (90\,\% utilized) system will have latency $10 T$, a 1\,\%
+       idle system (99\,\% utilized) will have latency $100 T$, and so on.
        This situation means that many latency-sensitive systems will
-       actively limit load, for example, to 50\%.
+       actively limit load, for example, to 50\,\%.
 \item  In the not-uncommon case where a given computed result is nice
        to have rather than critically important, use of timeouts can
        cause a blocking operation to have non-blocking properties that
-- 
2.43.0



Reply via email to