mirror of https://github.com/facebook/rocksdb.git
41849210e9
Summary: Fix compatibility with transparent huge pages by allocating in increments (1MiB) smaller than the typical smallest huge page size of 2MiB. Also, bypass the test when jemalloc config.fill is used, which means the allocator is explicitly configured to write to memory before we get it, which is not what this test expects. Fixes https://github.com/facebook/rocksdb/issues/12351 Pull Request resolved: https://github.com/facebook/rocksdb/pull/12378 Test Plan: ``` sudo bash -c 'echo "always" > /sys/kernel/mm/transparent_hugepage/enabled' ``` And see unit test fails before this change, passes after this change Also tested internal buck build with dbg mode (previously failing). Reviewed By: jaykorean, hx235 Differential Revision: D54139634 Pulled By: pdillinger fbshipit-source-id: 179accebe918d8eecd46a979fcf21d356f9b5519 |
||
---|---|---|
.. | ||
allocator.h | ||
arena.cc | ||
arena.h | ||
arena_test.cc | ||
concurrent_arena.cc | ||
concurrent_arena.h | ||
jemalloc_nodump_allocator.cc | ||
jemalloc_nodump_allocator.h | ||
memkind_kmem_allocator.cc | ||
memkind_kmem_allocator.h | ||
memory_allocator.cc | ||
memory_allocator_impl.h | ||
memory_allocator_test.cc | ||
memory_usage.h |