[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220211064917.2028469-1-shakeelb@google.com>
Date: Thu, 10 Feb 2022 22:49:13 -0800
From: Shakeel Butt <shakeelb@...gle.com>
To: Johannes Weiner <hannes@...xchg.org>,
Michal Hocko <mhocko@...e.com>, Roman Gushchin <guro@...com>
Cc: Chris Down <chris@...isdown.name>,
Andrew Morton <akpm@...ux-foundation.org>,
cgroups@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Shakeel Butt <shakeelb@...gle.com>
Subject: [PATCH v2 0/4] memcg: robust enforcement of memory.high
Due to the semantics of memory.high enforcement i.e. throttle the
workload without oom-kill, we are trying to use it for right sizing the
workloads in our production environment. However we observed the
mechanism fails for some specific applications which does big chunck of
allocations in a single syscall. The reason behind this failure is due
to the limitation of the memory.high enforcement's current
implementation. This patch series solves this issue by enforcing the
memory.high synchronously if the current process has accumulated a large
amount of high overcharge.
Changes since v1:
- Based on Roman's comment simply the sync enforcement and only target
the extreme cases.
Shakeel Butt (4):
memcg: refactor mem_cgroup_oom
memcg: unify force charging conditions
selftests: memcg: test high limit for single entry allocation
memcg: synchronously enforce memory.high for large overcharges
mm/memcontrol.c | 66 +++++++---------
tools/testing/selftests/cgroup/cgroup_util.c | 15 +++-
tools/testing/selftests/cgroup/cgroup_util.h | 1 +
.../selftests/cgroup/test_memcontrol.c | 78 +++++++++++++++++++
4 files changed, 120 insertions(+), 40 deletions(-)
--
2.35.1.265.g69c8d7142f-goog
Powered by blists - more mailing lists