On Sat, Jan 29, 2022 at 11:18:15PM +0100, Johann Klähn wrote:
> Signed-off-by: Johann Klähn <johann@xxxxxxxxxx>
> ---
> Hi Paul,
>
> I'm really enjoying the book and hope that I can contribute back a little bit in
> the form of small fixes. As this is my first patch to this list, please point
> out anything I could improve in the future (e.g., granularity of patches).
Queued and pushed, thank you! I did take the liberty of changing your
added "can" to a "nevertheless". Does that work for you?
Thanx, Paul
> Thanks
> Johann
> ---
> count/count.tex | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/count/count.tex b/count/count.tex
> index d2b39904..f4e74c13 100644
> --- a/count/count.tex
> +++ b/count/count.tex
> @@ -3237,7 +3237,7 @@ Summarizing the summary:
> \Cref{fig:count:Atomic Increment Scalability on x86}
> illustrates this point:
> Atomic increment might be completely acceptable for a two-CPU
> - system, but be completely inadequate for an eight-CPU system.
> + system, but can be completely inadequate for an eight-CPU system.
> \end{enumerate}
>
> \begin{figure}
> @@ -3251,7 +3251,7 @@ Summarizing still further, we have the ``big three'' methods of
> increasing performance and scalability, namely
> (1)~\emph{partitioning} over CPUs or threads,
> (2)~\emph{batching} so that more work can be done by each expensive
> -synchronization operations, and
> +synchronization operation, and
> (3)~\emph{weakening} synchronization operations where feasible.
> As a rough rule of thumb, you should apply these methods in this order,
> as was noted earlier in the discussion of
> --
> 2.34.1
>
