diff options
author | 2023-08-14 15:09:11 +0800 | |
---|---|---|
committer | 2023-08-16 12:21:32 +0100 | |
commit | ac8a52962164a50e693fa021d3564d7745b83a7f (patch) | |
tree | 8cafe2afe9f3308bf2dda05e24f8eb7bdf315420 /tools/perf/scripts/python | |
parent | nfp: update maintainer (diff) | |
download | wireguard-linux-ac8a52962164a50e693fa021d3564d7745b83a7f.tar.xz wireguard-linux-ac8a52962164a50e693fa021d3564d7745b83a7f.zip |
net-memcg: Fix scope of sockmem pressure indicators
Now there are two indicators of socket memory pressure sit inside
struct mem_cgroup, socket_pressure and tcpmem_pressure, indicating
memory reclaim pressure in memcg->memory and ->tcpmem respectively.
When in legacy mode (cgroupv1), the socket memory is charged into
->tcpmem which is independent of ->memory, so socket_pressure has
nothing to do with socket's pressure at all. Things could be worse
by taking socket_pressure into consideration in legacy mode, as a
pressure in ->memory can lead to premature reclamation/throttling
in socket.
While for the default mode (cgroupv2), the socket memory is charged
into ->memory, and ->tcpmem/->tcpmem_pressure are simply not used.
So {socket,tcpmem}_pressure are only used in default/legacy mode
respectively for indicating socket memory pressure. This patch fixes
the pieces of code that make mixed use of both.
Fixes: 8e8ae645249b ("mm: memcontrol: hook up vmpressure to socket pressure")
Signed-off-by: Abel Wu <wuyun.abel@bytedance.com>
Acked-by: Shakeel Butt <shakeelb@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions