This is an automated email from the git hooks/post-receive script.
sparks pushed a commit to branch master
in repository defensive-coding-guide.
commit eff2f5c71f3cd02e603dcd9e616a332f3490a0db
Author: Florian Weimer <fweimer(a)redhat.com>
Date: Thu Apr 10 21:10:41 2014 +0200
Custom memory allocators: Complete sentence
Also add section ID.
---
defensive-coding/en-US/C-Allocators.xml | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/defensive-coding/en-US/C-Allocators.xml
b/defensive-coding/en-US/C-Allocators.xml
index 1bff610..58c89ee 100644
--- a/defensive-coding/en-US/C-Allocators.xml
+++ b/defensive-coding/en-US/C-Allocators.xml
@@ -140,7 +140,7 @@
</para>
</section>
- <section>
+ <section id="sect-Defensive_Coding-C-Allocators-Custom">
<title>Custom memory allocators</title>
<para>
Custom memory allocates come in two forms: replacements for
@@ -176,7 +176,8 @@
allocators. In micro-benchmarks, pool allocators can show
huge wins, and size-specific pools can reduce internal
fragmentation. But often, utilization of individual pools
- is poor, and
+ is poor, and external fragmentation increases the overall
+ memory usage.
</para>
</listitem>
</itemizedlist>
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.