[PATCH -perfbook 4/5] datastruct: Expand on the dash type of traces in Figure 10.19

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The text reads "The uppermost three traces", but there appear
to be only two traces.
Put a footnote explaining how the dashed trace is composed.

Also mention the dash types in the text.

Signed-off-by: Akira Yokosawa <akiyks@xxxxxxxxx>
---
 datastruct/datastruct.tex | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/datastruct/datastruct.tex b/datastruct/datastruct.tex
index d8cab069..ba429dfc 100644
--- a/datastruct/datastruct.tex
+++ b/datastruct/datastruct.tex
@@ -1613,7 +1613,10 @@ fixed-size 524,288-bucket hash table, and a third for a resizable
 hash table that shifts back and forth between 262,144 and 524,288
 buckets, with a one-millisecond pause between each resize operation.
 
-The uppermost three traces are for the 262,144-element hash table.
+The uppermost three traces are for the 262,144-element hash table.\footnote{
+	You see only two traces?
+	The dashed one is composed of two traces that differ
+	only slightly, hence the irregular-looking dash pattern.}
 The dashed trace corresponds to the two fixed-size hash tables,
 and the solid trace to the resizable hash table.
 In this case, the short hash chains cause normal lookup overhead
@@ -1626,10 +1629,10 @@ In particular, the entire hash table fits into L3 cache.
 % millisecond is clearly too short a time.
 
 The lower three traces are for the 2,097,152-element hash table.
-The upper trace corresponds to the 262,144-bucket fixed-size hash table,
-the trace in the middle for low CPU counts and at the bottom for high
-CPU counts to the resizable hash table, and the other trace
-to the 524,288-bucket fixed-size hash table.
+The upper dashed trace corresponds to the 262,144-bucket fixed-size
+hash table, the solid trace in the middle for low CPU counts and at
+the bottom for high CPU counts to the resizable hash table,
+and the other trace to the 524,288-bucket fixed-size hash table.
 The fact that there are now an average of eight elements per bucket
 can only be expected to produce a sharp decrease in performance,
 as in fact is shown in the graph.
-- 
2.17.1





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux