On Thu, Jan 08, 2015 at 11:15:04PM -0500, Johannes Weiner wrote: > - memory.low configures the lower end of the cgroup's expected > memory consumption range. The kernel considers memory below that > boundary to be a reserve - the minimum that the workload needs in > order to make forward progress - and generally avoids reclaiming > it, unless there is an imminent risk of entering an OOM situation. AFAICS, if a cgroup cannot be shrunk back to its low limit (e.g. because it consumes anon memory, and there's no swap), it will get on with it. Is it considered to be a problem? Are there any plans to fix it, e.g. by invoking OOM-killer in a cgroup that is above its low limit if we fail to reclaim from it? Thanks, Vladimir -- 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
