mirror of
https://github.com/MariaDB/server.git
synced 2026-10-23 18:49:29 +03:00
072c7dc774
my_large_virtual_alloc(): If large page allocation fails, clear my_use_large_pages. Outside large page allocation (and IBM AIX), invoke mmap(2) with PROT_NONE so that no page table entries will have to be allocated. Also, fix the error reporting. my_virtual_mem_commit(): Do not set the Linux specific flag MAP_POPULATE because it would introduce a performance regression on startup. There is a better, system-wide way to disable the overcommit: sudo sysctl vm.overcommit_memory=2 HAVE_UNACCESSIBLE_AFTER_MEM_DECOMMIT: Remove. We will always make the virtual memory unaccessible, so that the operating system can deallocate the page table entries. buf_pool_t::create(): Skip the my_virtual_mem_commit() on AIX only. buf_pool_t::page_guess(): Unconditionally check if the pointer is within the currently allocated buffer pool. innodb_buffer_pool_size_max: On 64-bit systems other than IBM AIX, we will default to 8 TiB. On 32-bit systems, we retain the default innodb_buffer_pool_size_max=0, that is, by default, SET GLOBAL innodb_buffer_pool_size=... will be unable to increase from the initial value. There is no functional change to the startup logic that adjusts innodb_buffer_pool_size_max to be at least innodb_buffer_pool_size rounded up to the extent size (2 MiB on 32-bit, 8 MiB on 64-bit).