Skip to content

Commit

Permalink
doc-cgroup-update-note-about-conditions-when-oom-killer-is-invoked-fix
Browse files Browse the repository at this point in the history 
fixes per Randy

Cc: Konstantin Khlebnikov <[email protected]>
Cc: Michal Hocko <[email protected]>
Cc: Randy Dunlap <[email protected]>
Cc: Roman Gushchin <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
Signed-off-by: Stephen Rothwell <[email protected]>
  • Loading branch information
@akpm00 @sfrothwell
akpm00 authored and sfrothwell committed Jun 5, 2020
1 parent ca9c7de commit e892283
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions Documentation/admin-guide/cgroup-v2.rst
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1170,8 +1170,8 @@ PAGE_SIZE multiple when read back.
Under certain circumstances, the usage may go over the limit
temporarily.

In default configuration regular 0-order allocation always
succeed unless OOM killer choose current task as a victim.
In default configuration regular 0-order allocations always
succeed unless OOM killer chooses current task as a victim.

Some kinds of allocations don't invoke the OOM killer.
Caller could retry them differently, return into userspace
Expand Down

0 comments on commit e892283

Please sign in to comment.