On Tue, Mar 04, 2014 at 07:59:41PM -0800, David Rientjes wrote: > Now that process handling system oom conditions have access to a small > amount of memory reserves, we need a way to notify those process on > system oom conditions. > > When a userspace process waits on the root memcg's memory.oom_control, it > will wake up anytime there is a system oom condition. > > This is a special case of oom notifiers since it doesn't subsequently > notify all memcgs under the root memcg (all memcgs on the system). We > don't want to trigger those oom handlers which are set aside specifically > for true memcg oom notifications that disable their own oom killers to > enforce their own oom policy, for example. > > Signed-off-by: David Rientjes <rientjes@xxxxxxxxxx> Until consensus on the whole approach can be reached, Nacked-by: Tejun Heo <tj@xxxxxxxxxx> Thanks. -- tejun -- 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
