| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
In the process, kill arena_bin_index, which is unused. To follow are several
diffs continuing this separation.
|
| |
|
|
| |
The test assumes no sampled allocations.
|
| |
|
|
|
|
|
|
|
|
| |
When allocating from dirty extents (which we always prefer if available), large
active extents can get split even if the new allocation is much smaller, in
which case the introduced fragmentation causes high long term damage. This new
option controls the threshold to reuse and split an existing active extent. We
avoid using a large extent for much smaller sizes, in order to reduce
fragmentation. In some workload, adding the threshold improves virtual memory
usage by >10x.
|
| |
|
|
|
|
|
| |
This option controls the max size when grow_retained. This is useful when we
have customized extent hooks reserving physical memory (e.g. 1G huge pages).
Without this feature, the default increasing sequence could result in fragmented
and wasted physical memory.
|
| |
|
|
|
| |
Currently, this is unused (i.e. all extents are always marked dumpable). In the
future, we'll begin using this functionality.
|
| |
|
|
| |
Dodge a name-conflict with the math.h logarithm function. D'oh.
|
| |
|
|
|
| |
Huge pages could be disabled even if the kernel header has MAD_HUGEPAGE
defined. Guard the huge pagetest with runtime detection.
|
| |
|
|
| |
Report number of THPs used in arena and aggregated stats.
|
| |
|
|
|
|
|
|
| |
To avoid the high RSS caused by THP + low usage arena (i.e. THP becomes a
significant percentage), added a new "auto" option which will only start using
THP after a base allocator used up the first THP region. Starting from the
second hugepage (in a single arena), "auto" behaves the same as "always",
i.e. madvise hugepage right away.
|
| |
|
|
| |
The abort_conf option was missed from test/unit/mallctl.
|
| |
|
|
|
|
| |
As part of the metadata_thp support, We now have a separate swtich
(JEMALLOC_HAVE_MADVISE_HUGE) for MADV_HUGEPAGE availability. Use that instead
of JEMALLOC_THP (which doesn't guard pages_huge anymore) in tests.
|
| |
|
|
|
| |
This option enables transparent huge page for base allocators (require
MADV_HUGEPAGE support).
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently we have to log by writing something like:
static log_var_t log_a_b_c = LOG_VAR_INIT("a.b.c");
log (log_a_b_c, "msg");
This is sort of annoying. Let's just write:
log("a.b.c", "msg");
|
| |
|
|
|
|
| |
Currently, the log macro requires at least one argument after the format string,
because of the way the preprocessor handles varargs macros. We can hide some of
that irritation by pushing the extra arguments into a varargs function.
|
| |
|
|
|
| |
This sets up a hierarchical logging facility, so that we can add logging
statements liberally, and turn them on in a fine-grained manner.
|
| |
|
|
|
|
| |
Forking a multithreaded process is dangerous but allowed, so long as the child
only executes async-signal-safe functions (e.g. exec). Add a test to ensure
that we don't break this behavior.
|
| |
|
|
|
| |
Customized extent hooks may malloc / free thus trigger reentry. Support this
behavior by adding reentrancy on hook functions.
|
| |
|
|
|
| |
We lookup freed extents for testing in post_reset. Take background_thread lock
so that the extents are not modified at the same time.
|
| | |
|
| |
|
|
|
| |
Since tsd cleanup isn't guaranteed when reincarnated, we set up tsd in a way
that needs no cleanup, by making it going through slow path instead.
|
| |
|
|
|
|
| |
Add testing for background_thread:true, and condition a xallocx() -->
rallocx() escalation assertion to allow for spurious in-place rallocx()
following xallocx() failure.
|
| |
|
|
|
| |
Refactor bootstrapping such that dlsym() is called during the
bootstrapping phase that can tolerate reentrant allocation.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This resolves #669.
|
| | |
|
| | |
|
| |
|
|
| |
h_step_sum was used to compute moving sum. Not in use anymore.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Added opt.background_thread to enable background threads, which handles purging
currently. When enabled, decay ticks will not trigger purging (which will be
left to the background threads). We limit the max number of threads to NCPUs.
When percpu arena is enabled, set CPU affinity for the background threads as
well.
The sleep interval of background threads is dynamic and determined by computing
number of pages to purge in the future (based on backlog).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of embedding a lock bit in rtree leaf elements, we associate extents
with a small set of mutexes. This gets us two things:
- We can use the system mutexes. This (hypothetically) protects us from
priority inversion, and lets us stop doing a backoff/sleep loop, instead
opting for precise wakeups from the mutex.
- Cuts down on the number of mutex acquisitions we have to do (from 4 in the
worst case to two).
We end up simplifying most of the rtree code (which no longer has to deal with
locking or concurrency at all), at the cost of additional complexity in the
extent code: since the mutex protecting the rtree leaf elements is determined by
reading the extent out of those elements, the initial read is racy, so that we
may acquire an out of date mutex. We re-check the extent in the leaf after
acquiring the mutex to protect us from this race.
|
| |
|
|
|
|
|
|
| |
Support millisecond resolution for decay times. Among other use cases
this makes it possible to specify a short initial dirty-->muzzy decay
phase, followed by a longer muzzy-->clean decay phase.
This resolves #812.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This removes the tsd macros (which are used only for tsd_t in real builds). We
break up the circular dependencies involving tsd.
We also move all tsd access through getters and setters. This allows us to
assert that we only touch data when tsd is in a valid state.
We simplify the usages of the x macro trick, removing all the customizability
(get/set, init, cleanup), moving the lifetime logic to tsd_init and tsd_cleanup.
This lets us make initialization order independent of order within tsd_t.
|
| |
|
|
|
|
|
|
|
|
| |
Add the extent_destroy_t extent destruction hook to extent_hooks_t, and
use it during arena destruction. This hook explicitly communicates to
the callee that the extent must be destroyed or tracked for later reuse,
lest it be permanently leaked. Prior to this change, retained extents
could unintentionally be leaked if extent retention was enabled.
This resolves #560.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Control use of munmap(2) via a run-time option rather than a
compile-time option (with the same per platform default). The old
behavior of --disable-munmap can be achieved with
--with-malloc-conf=munmap:false.
This partially resolves #580.
|
| | |
|
| |
|
|
|
|
|
| |
This option is no longer useful, because TLS is correctly configured
automatically on all supported platforms.
This partially resolves #580.
|
| |
|
|
|
|
|
|
|
|
|
| |
Simplify configuration by removing the --disable-tcache option, but
replace the testing for that configuration with
--with-malloc-conf=tcache:false.
Fix the thread.arena and thread.tcache.flush mallctls to work correctly
if tcache is disabled.
This partially resolves #580.
|
| |
|
|
|
|
|
|
|
| |
All mappings continue to be PAGE-aligned, even if the system page size
is smaller. This change is primarily intended to provide a mechanism
for supporting multiple page sizes with the same binary; smaller page
sizes work better in conjunction with jemalloc's design.
This resolves #467.
|
| |
|
|
|
|
|
|
|
| |
Some systems use a native 64 KiB page size, which means that the bitmap
for the smallest size class can be 8192 bits, not just 512 bits as when
the page size is 4 KiB. Linear search in bitmap_{sfu,ffu}() is
unacceptably slow for such large bitmaps.
This reverts commit 7c00f04ff40a34627e31488d02ff1081c749c7ba.
|
| | |
|
| | |
|
| |
|
|
| |
This enables stable sorting of extent_t structures.
|
