Re: [PATCH v2] mm: memcontrol: protect the memory in cgroup from being oom killed

On Thu 08-12-22 14:07:06, 程垲涛 Chengkaitao Cheng wrote:

At 2022-12-08 16:14:10, "Michal Hocko" [off-list ref] wrote:

quoted

On Thu 08-12-22 07:59:27, 程垲涛 Chengkaitao Cheng wrote:

quoted

At 2022-12-08 15:33:07, "Michal Hocko" [off-list ref] wrote:

quoted

On Thu 08-12-22 11:46:44, chengkaitao wrote:

quoted

From: chengkaitao <redacted>

We created a new interface <memory.oom.protect> for memory, If there is
the OOM killer under parent memory cgroup, and the memory usage of a
child cgroup is within its effective oom.protect boundary, the cgroup's
tasks won't be OOM killed unless there is no unprotected tasks in other
children cgroups. It draws on the logic of <memory.min/low> in the
inheritance relationship.

It has the following advantages,
1. We have the ability to protect more important processes, when there
is a memcg's OOM killer. The oom.protect only takes effect local memcg,
and does not affect the OOM killer of the host.
2. Historically, we can often use oom_score_adj to control a group of
processes, It requires that all processes in the cgroup must have a
common parent processes, we have to set the common parent process's
oom_score_adj, before it forks all children processes. So that it is
very difficult to apply it in other situations. Now oom.protect has no
such restrictions, we can protect a cgroup of processes more easily. The
cgroup can keep some memory, even if the OOM killer has to be called.

Signed-off-by: chengkaitao <redacted>
---
v2: Modify the formula of the process request memcg protection quota.

The new formula doesn't really address concerns expressed previously.
Please read my feedback carefully again and follow up with questions if
something is not clear.

The previous discussion was quite scattered. Can you help me summarize
your concerns again?

The most important part is http://lkml.kernel.org/r/Y4jFnY7kMdB8ReSW@dhcp22.suse.cz
: Let me just emphasise that we are talking about fundamental disconnect.
: Rss based accounting has been used for the OOM killer selection because
: the memory gets unmapped and _potentially_ freed when the process goes
: away. Memcg changes are bound to the object life time and as said in
: many cases there is no direct relation with any process life time.

We need to discuss the relationship between memcg's mem and process's mem, 

task_usage = task_anon(rss_anon) + task_mapped_file(rss_file) 
	 + task_mapped_share(rss_share) + task_pgtables + task_swapents

memcg_usage	= memcg_anon + memcg_file + memcg_pgtables + memcg_share
	= all_task_anon + all_task_mapped_file + all_task_mapped_share 
	 + all_task_pgtables + unmapped_file + unmapped_share
	= all_task_usage + unmapped_file + unmapped_share - all_task_swapents

You are missing all the kernel charged objects (aka __GFP_ACCOUNT
allocations resp. SLAB_ACCOUNT for slab caches). Depending on the
workload this can be really a very noticeable portion. So not this is
not just about unmapped cache or shm.

quoted

That is to the per-process discount based on rss or any per-process
memory metrics.

Another really important question is the actual configurability. The
hierarchical protection has to be enforced and that means that same as
memory reclaim protection it has to be enforced top-to-bottom in the
cgroup hierarchy. That makes the oom protection rather non-trivial to
configure without having a good picture of a larger part of the cgroup
hierarchy as it cannot be tuned based on a reclaim feedback.

There is an essential difference between reclaim and oom killer.

oom killer is a memory reclaim of the last resort. So yes, there is some
difference but fundamentally it is about releasing some memory. And long
term we have learned that the more clever it tries to be the more likely
corner cases can happen. It is simply impossible to know the best
candidate so this is a just a best effort. We try to aim for
predictability at least.

The reclaim 
cannot be directly perceived by users,

I very strongly disagree with this statement. First the direct reclaim is a
direct source of latencies because the work is done on behalf of the
allocating process. There are side effect possible as well because
refaults have their cost as well.

so memcg need to count indicators 
similar to pgscan_(kswapd/direct). However, when the user process is killed 
by oom killer, users can clearly perceive and count (such as the number of 
restarts of a certain type of process). At the same time, the kernel also has 
memory.events to count some information about the oom killer, which can 
also be used for feedback adjustment.

Yes we have those metrics already. I suspect I haven't made myself
clear. I didn't say there are no measures to see how oom behaves. What
I've said that I _suspect_ that oom protection would be really hard to
configure correctly because unlike the memory reclaim which happens
during the normal operation, oom is a relatively rare event and it is
quite hard to use it for any feedback mechanisms. But I am really open
to be convinced otherwise and this is in fact what I have been asking
for since the beginning. I would love to see some examples on the
reasonable configuration for a practical usecase. It is one thing to say
that you can set the protection to a certain value and a different one
to have a way to determine that value. See my point?

-- 
Michal Hocko
SUSE Labs