Re: user defined OOM policies

[David Rientjes]

On Wed, 20 Nov 2013, Michal Hocko wrote:

> OK, I was a bit vague it seems. I meant to give zonelist, gfp_mask,
> allocation order and nodemask parameters to the modules. So they have a
> better picture of what is the OOM context.
> What everything ould modules need to do an effective work is a matter
> for discussion.
> 

It's an interesting idea but unfortunately a non-starter for us because 
our users don't have root, we create their memcg tree and then chown it to 
the user.  They can freely register for oom notifications but cannot load 
their own kernel modules for their own specific policy.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/