[lkml]   [2019]   [May]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH REBASED] mm, memcg: Make scan aggression always exclude protection
Michal Hocko writes:
>Maybe I am missing something so correct me if I am wrong but the new
>calculation actually means that we always allow to scan even min
>protected memcgs right?

We check if the memcg is min protected as a precondition for coming into this
function at all, so this generally isn't possible. See the mem_cgroup_protected
MEMCG_PROT_MIN check in shrink_node.

(Of course, it's possible we race with going within protection thresholds
again, but this patch doesn't make that any better or worse than the previous

 \ /
  Last update: 2019-05-30 08:45    [W:0.256 / U:1.180 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site