Hi > On Mon, 11 Apr 2011 14:31:18 +0900 (JST) > KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx> wrote: > > > This is a almost revert commit 93b43fa (oom: give the dying > > task a higher priority). > > > > The commit dramatically improve oom killer logic when fork-bomb > > occur. But, I've found it has nasty corner case. Now cpu cgroup > > has strange default RT runtime. It's 0! That said, if a process > > under cpu cgroup promote RT scheduling class, the process never > > run at all. > > hm. How did that happen? I thought that sched_setscheduler() modifies > only a single thread, and that thread is in the process of exiting? If admin insert !RT process into a cpu cgroup of setting rtruntime=0, usually it run perfectly because !RT task isn't affected from rtruntime knob, but If it promote RT task, by explicit setscheduler() syscall or OOM, the task can't run at all. In short, now oom killer don't work at all if admin are using cpu cgroup and don't touch rtruntime knob. -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>