Hi > Hi, Kosaki. > > On Sat, May 29, 2010 at 12:59 PM, KOSAKI Motohiro > <kosaki.motohiro@xxxxxxxxxxxxxx> wrote: > > Hi > > > >> oom-killer: give the dying task rt priority (v3) > >> > >> Give the dying task RT priority so that it can be scheduled quickly and die, > >> freeing needed memory. > >> > >> Signed-off-by: Luis Claudio R. Gonçalves <lgoncalv@xxxxxxxxxx> > > > > Almostly acceptable to me. but I have two requests, > > > > - need 1) force_sig() 2)sched_setscheduler() order as Oleg mentioned > > - don't boost priority if it's in mem_cgroup_out_of_memory() > > Why do you want to not boost priority if it's path of memcontrol? > > If it's path of memcontrol and CONFIG_CGROUP_MEM_RES_CTLR is enabled, > mem_cgroup_out_of_memory will select victim task in memcg. > So __oom_kill_task's target task would be in memcg, I think. Yep. But priority boost naturally makes CPU starvation for out of the group processes. It seems to break cgroup's isolation concept. > As you and memcg guys don't complain this, I would be missing something. > Could you explain it? :) So, My points are, 1) Usually priority boost is wrong idea. It have various side effect, but system wide OOM is one of exception. In such case, all tasks aren't runnable, then, the downside is acceptable. 2) memcg have OOM notification mechanism. If the admin need priority boost, they can do it by their OOM-daemon. Thanks. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>