On Wed, May 25, 2016 at 11:51 PM, Michal Hocko <mhocko@xxxxxxxxxx> wrote: > This is quite hard for me to grasp. What would you say about the > following: > " > mem_cgroup_margin might return memory.limit - memory_count when > the memsw.limit is in excess. This > doesn't happen usually because we do not allow excess on hard limits and > memory.limit <= memsw.limit but __GFP_NOFAIL charges can force the charge > and cause the excess when no memory is really swapable (swap is full or > no anonymous memory is left). Sorry for my poor English, thanks for your description, hope it can be into the log -Roy -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
