lkml.org 
[lkml]   [2017]   [Dec]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v13 6/7] mm, oom, docs: describe the cgroup-aware OOM killer
On Fri 01-12-17 17:01:49, Roman Gushchin wrote:
[...]
> diff --git a/Documentation/cgroup-v2.txt b/Documentation/cgroup-v2.txt
> index c80a147f94b7..ff8e92db636d 100644
> --- a/Documentation/cgroup-v2.txt
> +++ b/Documentation/cgroup-v2.txt
> @@ -1049,6 +1049,9 @@ PAGE_SIZE multiple when read back.
> and will never kill the unkillable task, even if memory.oom_group
> is set.
>
> + If cgroup-aware OOM killer is not enabled, ENOTSUPP error
> + is returned on attempt to access the file.
> +
> memory.events
> A read-only flat-keyed file which exists on non-root cgroups.
> The following entries are defined. Unless specified
> @@ -1258,6 +1261,12 @@ OOM Killer
> Cgroup v2 memory controller implements a cgroup-aware OOM killer.
> It means that it treats cgroups as first class OOM entities.
>
> +Cgroup-aware OOM logic is turned off by default and requires
> +passing the "groupoom" option on mounting cgroupfs. It can also
> +by remounting cgroupfs with the following command::
> +
> + # mount -o remount,groupoom $MOUNT_POINT
> +
> Under OOM conditions the memory controller tries to make the best
> choice of a victim, looking for a memory cgroup with the largest
> memory footprint, considering leaf cgroups and cgroups with the

Looks good to me

Thanks!
--
Michal Hocko
SUSE Labs

\
 
 \ /
  Last update: 2017-12-01 18:14    [W:0.168 / U:0.272 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site