aboutsummaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorJason Evans <je@fb.com>2012-02-13 12:36:11 -0800
committerJason Evans <je@fb.com>2012-02-13 12:36:11 -0800
commit0fee70d718b9846cfab04225dc86a4b4216b963f (patch)
tree9d63b65a61fe7ff3ba5a60f37d9afb1b0ae806fb /INSTALL
parent6ffbbeb5d60bdf16e15927cb1f173376fe355449 (diff)
downloadjemalloc-0fee70d718b9846cfab04225dc86a4b4216b963f.tar.gz
Do not enable lazy locking by default.
Do not enable lazy locking by default, because: - It's fragile (applications can subvert detection of multi-threaded mode). - Thread caching amortizes locking overhead in the default configuration.
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL4
1 files changed, 2 insertions, 2 deletions
diff --git a/INSTALL b/INSTALL
index fa32d05..a210ec5 100644
--- a/INSTALL
+++ b/INSTALL
@@ -128,8 +128,8 @@ any of the following arguments (not a definitive list) to 'configure':
a measurable impact on performance, since the compiler is forced to load
the page size from memory rather than embedding immediate values.
---disable-lazy-lock
- Disable code that wraps pthread_create() to detect when an application
+--enable-lazy-lock
+ Enable code that wraps pthread_create() to detect when an application
switches from single-threaded to multi-threaded mode, so that it can avoid
mutex locking/unlocking operations while in single-threaded mode. In
practice, this feature usually has little impact on performance unless