summaryrefslogtreecommitdiffstats
path: root/io_uring
diff options
context:
space:
mode:
authorAbel Wu <wuyun.abel@bytedance.com>2023-08-14 15:09:11 +0800
committerDavid S. Miller <davem@davemloft.net>2023-08-16 12:21:32 +0100
commitac8a52962164a50e693fa021d3564d7745b83a7f (patch)
tree8cafe2afe9f3308bf2dda05e24f8eb7bdf315420 /io_uring
parent7fd034bce6d276353a4e70c516789dfe6b2c32ae (diff)
downloadlinux-ac8a52962164a50e693fa021d3564d7745b83a7f.tar.gz
linux-ac8a52962164a50e693fa021d3564d7745b83a7f.tar.bz2
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 'io_uring')
0 files changed, 0 insertions, 0 deletions