diff options
author | Vlastimil Babka <vbabka@suse.cz> | 2025-09-26 15:50:25 +0200 |
---|---|---|
committer | Vlastimil Babka <vbabka@suse.cz> | 2025-09-29 09:46:17 +0200 |
commit | ca74b8cadaad4b179f77f1f4dc3d288be9a580f1 (patch) | |
tree | b630614b598a5b9405a93edb8e6850c26dc3787f /scripts/gdb/linux/timerlist.py | |
parent | b9120619246d733a27e5e93c29e86f2e0401cfc5 (diff) | |
parent | af92793e52c3a99b828ed4bdd277fd3e11c18d08 (diff) |
Merge series "slab: Re-entrant kmalloc_nolock()"
From the cover letter [1]:
This patch set introduces kmalloc_nolock() which is the next logical
step towards any context allocation necessary to remove bpf_mem_alloc
and get rid of preallocation requirement in BPF infrastructure.
In production BPF maps grew to gigabytes in size. Preallocation wastes
memory. Alloc from any context addresses this issue for BPF and other
subsystems that are forced to preallocate too.
This long task started with introduction of alloc_pages_nolock(), then
memcg and objcg were converted to operate from any context including
NMI, this set completes the task with kmalloc_nolock() that builds on
top of alloc_pages_nolock() and memcg changes.
After that BPF subsystem will gradually adopt it everywhere.
Link: https://lore.kernel.org/all/20250909010007.1660-1-alexei.starovoitov@gmail.com/ [1]
Diffstat (limited to 'scripts/gdb/linux/timerlist.py')
0 files changed, 0 insertions, 0 deletions