diff options
| author | Jason Evans <je@fb.com> | 2012-02-13 22:30:52 (GMT) |
|---|---|---|
| committer | Jason Evans <je@fb.com> | 2012-02-13 23:03:59 (GMT) |
| commit | ef8897b4b938111fcc9b54725067f1dbb33a4c20 (patch) | |
| tree | 46e59a294ec4b435432de0f2bd9412f5caaec9b7 /INSTALL | |
| parent | 0fee70d718b9846cfab04225dc86a4b4216b963f (diff) | |
| download | jemalloc-ef8897b4b938111fcc9b54725067f1dbb33a4c20.zip jemalloc-ef8897b4b938111fcc9b54725067f1dbb33a4c20.tar.gz jemalloc-ef8897b4b938111fcc9b54725067f1dbb33a4c20.tar.bz2 | |
Make 8-byte tiny size class non-optional.
When tiny size class support was first added, it was intended to support
truly tiny size classes (even 2 bytes). However, this wasn't very
useful in practice, so the minimum tiny size class has been limited to
sizeof(void *) for a long time now. This is too small to be standards
compliant, but other commonly used malloc implementations do not even
bother using a 16-byte quantum on systems with vector units (SSE2+,
AltiVEC, etc.). As such, it is safe in practice to support an 8-byte
tiny size class on 64-bit systems that support 16-byte types.
Diffstat (limited to 'INSTALL')
| -rw-r--r-- | INSTALL | 7 |
1 files changed, 0 insertions, 7 deletions
@@ -90,13 +90,6 @@ any of the following arguments (not a definitive list) to 'configure': Statically link against the specified libunwind.a rather than dynamically linking with -lunwind. ---disable-tiny - Disable tiny (sub-quantum-sized) object support. Technically it is not - legal for a malloc implementation to allocate objects with less than - quantum alignment (8 or 16 bytes, depending on architecture), but in - practice it never causes any problems if, for example, 4-byte allocations - are 4-byte-aligned. - --disable-tcache Disable thread-specific caches for small objects. Objects are cached and released in bulk, thus reducing the total number of mutex operations. See |