Well, I thought the system would only load one OOM policy(set one policy name), which would set the prio of all memcgs.
Delete set_oom_policy_name, it makes no sense for users to set policy names. 🙂
There can be multiple OOM policy in the system at the same time.
If we need to apply different OOM policies to different memcgs based on different scenarios, we can use this hook(set_oom_policy_name) to set name to identify which policy in invoked at that time.
Just some thoughts.