diff options
author | 2024-10-28 19:53:41 +0800 | |
---|---|---|
committer | 2024-11-11 10:56:27 -0800 | |
commit | 0c3ce2f50261cd2f654d931eeb933c370a3a7d7a (patch) | |
tree | 725171e0fde46cb1426a36efd7355e9426132bb7 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | xtensa: remove the get_order() implementation (diff) | |
download | wireguard-linux-0c3ce2f50261cd2f654d931eeb933c370a3a7d7a.tar.xz wireguard-linux-0c3ce2f50261cd2f654d931eeb933c370a3a7d7a.zip |
mm: page_frag: reuse existing space for 'size' and 'pfmemalloc'
Currently there is one 'struct page_frag' for every 'struct
sock' and 'struct task_struct', we are about to replace the
'struct page_frag' with 'struct page_frag_cache' for them.
Before begin the replacing, we need to ensure the size of
'struct page_frag_cache' is not bigger than the size of
'struct page_frag', as there may be tens of thousands of
'struct sock' and 'struct task_struct' instances in the
system.
By or'ing the page order & pfmemalloc with lower bits of
'va' instead of using 'u16' or 'u32' for page size and 'u8'
for pfmemalloc, we are able to avoid 3 or 5 bytes space waste.
And page address & pfmemalloc & order is unchanged for the
same page in the same 'page_frag_cache' instance, it makes
sense to fit them together.
After this patch, the size of 'struct page_frag_cache' should be
the same as the size of 'struct page_frag'.
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux-MM <linux-mm@kvack.org>
Signed-off-by: Yunsheng Lin <linyunsheng@huawei.com>
Reviewed-by: Alexander Duyck <alexanderduyck@fb.com>
Link: https://patch.msgid.link/20241028115343.3405838-7-linyunsheng@huawei.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions