mirror of
https://github.com/jemalloc/jemalloc.git
synced 2026-08-24 16:13:38 +03:00
Rename huge_threshold to oversize_threshold.
The keyword huge tend to remind people of huge pages which is not relevent to the feature.
This commit is contained in:
parent
350809dc5d
commit
e3db480f6f
10 changed files with 24 additions and 26 deletions
|
|
@ -1240,15 +1240,15 @@ malloc_conf_init(sc_data_t *sc_data, unsigned bin_shard_sizes[SC_NBINS]) {
|
|||
-1, (sizeof(size_t) << 3) - 1)
|
||||
|
||||
/*
|
||||
* The runtime option of huge_threshold remains
|
||||
* The runtime option of oversize_threshold remains
|
||||
* undocumented. It may be tweaked in the next major
|
||||
* release (6.0). The default value 8M is rather
|
||||
* conservative / safe. Tuning it further down may
|
||||
* improve fragmentation a bit more, but may also cause
|
||||
* contention on the huge arena.
|
||||
*/
|
||||
CONF_HANDLE_SIZE_T(opt_huge_threshold,
|
||||
"huge_threshold", SC_LARGE_MINCLASS,
|
||||
CONF_HANDLE_SIZE_T(opt_oversize_threshold,
|
||||
"oversize_threshold", SC_LARGE_MINCLASS,
|
||||
SC_LARGE_MAXCLASS, yes, yes, false)
|
||||
CONF_HANDLE_SIZE_T(opt_lg_extent_max_active_fit,
|
||||
"lg_extent_max_active_fit", 0,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue