On Tue, Mar 04, 2014 at 07:59:19PM -0800, David Rientjes wrote: > Userspace needs a way to define the amount of memory reserves that > processes handling oom conditions may utilize. This patch adds a per- > memcg oom reserve field and file, memory.oom_reserve_in_bytes, to > manipulate its value. > > If currently utilized memory reserves are attempted to be reduced by > writing a smaller value to memory.oom_reserve_in_bytes, it will fail with > -EBUSY until some memory is uncharged. > > Signed-off-by: David Rientjes <rientjes@xxxxxxxxxx> We're completely unsure this is the way we wanna be headed and this is a huge commitment. For now at least, Nacked-by: Tejun Heo <tj@xxxxxxxxxx> -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
