diff options
author | Brian Behlendorf <[email protected]> | 2021-06-03 13:37:45 -0700 |
---|---|---|
committer | GitHub <[email protected]> | 2021-06-03 14:37:45 -0600 |
commit | 783784582225e8ddfbf07993d9fc278bf08025c5 (patch) | |
tree | 37c50b63885f8564c4d8ad8db5acfc7395409f70 /man/man8 | |
parent | 739cfb965b00e9cc3155c4a0d6c24bd779b1a245 (diff) |
Linux: Set spl_kmem_cache_slab_limit when page size !4K
For small objects the kernel's slab implementation is very fast and
space efficient. However, as the allocation size increases to
require multiple pages performance suffers. The SPL kmem cache
allocator was designed to better handle these large allocation
sizes. Therefore, on Linux the kmem_cache_* compatibility wrappers
prefer to use the kernel's slab allocator for small objects and
the custom SPL kmem cache allocator for larger objects.
This logic was effectively disabled for all architectures using
a non-4K page size which caused all kmem caches to only use the
SPL implementation. Functionally this is fine, but the SPL code
which calculates the target number of objects per-slab does not
take in to account that __vmalloc() always returns page-aligned
memory. This can result in a massive amount of wasted space when
allocating tiny objects on a platform using large pages (64k).
To resolve this issue we set the spl_kmem_cache_slab_limit cutoff
to 16K for all architectures.
This particular change does not attempt to update the logic used
to calculate the optimal number of pages per slab. This remains
an issue which should be addressed in a future change.
Reviewed-by: Matthew Ahrens <[email protected]>
Reviewed-by: Tony Nguyen <[email protected]>
Signed-off-by: Brian Behlendorf <[email protected]>
Closes #12152
Closes #11429
Closes #11574
Closes #12150
Diffstat (limited to 'man/man8')
0 files changed, 0 insertions, 0 deletions