diff options
| author |   MengEn Sun <mengensun@tencent.com> | 2024-11-01 12:06:38 +0800 |
|---|---|---|
| committer |   Andrew Morton <akpm@linux-foundation.org> | 2024-11-14 22:49:19 -0800 |
| commit | 2ea80b039b9af0b71c00378523b71c254fb99c23 (patch) | |
| tree | 595a63bff410f556f4606ee2f3d9aecebb8b8e33 /scripts/gdb/linux/modules.py | |
| parent | mm: mmap_lock: check trace_mmap_lock_$type_enabled() instead of regcount (diff) | |
| download | wireguard-linux-2ea80b039b9af0b71c00378523b71c254fb99c23.tar.xz wireguard-linux-2ea80b039b9af0b71c00378523b71c254fb99c23.zip | |
vmstat: call fold_vm_zone_numa_events() before show per zone NUMA event
Since 5.14-rc1, NUMA events will only be folded from per-CPU statistics to
per zone and global statistics when the user actually needs it.
Currently, the kernel has performs the fold operation when reading
/proc/vmstat, but does not perform the fold operation in /proc/zoneinfo.
This can lead to inaccuracies in the following statistics in zoneinfo:
- numa_hit
- numa_miss
- numa_foreign
- numa_interleave
- numa_local
- numa_other
Therefore, before printing per-zone vm_numa_event when reading
/proc/zoneinfo, we should also perform the fold operation.
Link: https://lkml.kernel.org/r/1730433998-10461-1-git-send-email-mengensun@tencent.com
Fixes: f19298b9516c ("mm/vmstat: convert NUMA statistics to basic NUMA counters")
Signed-off-by: MengEn Sun <mengensun@tencent.com>
Reviewed-by: JinLiang Zheng <alexjlzheng@tencent.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Diffstat (limited to 'scripts/gdb/linux/modules.py')
0 files changed, 0 insertions, 0 deletions