summaryrefslogtreecommitdiffstats
path: root/Documentation/io-mapping.txt
diff options
context:
space:
mode:
authorKOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>2011-04-15 00:22:13 +0200
committerLinus Torvalds <torvalds@linux-foundation.org>2011-04-15 01:06:56 +0200
commit341aea2bc48bf652777fb015cc2b3dfa9a451817 (patch)
tree46846e06674fdf45542ed3101c7a55aa31a577af /Documentation/io-mapping.txt
parentvmscan: all_unreclaimable() use zone->all_unreclaimable as a name (diff)
downloadlinux-341aea2bc48bf652777fb015cc2b3dfa9a451817.tar.xz
linux-341aea2bc48bf652777fb015cc2b3dfa9a451817.zip
oom-kill: remove boost_dying_task_prio()
This is an almost-revert of commit 93b43fa ("oom: give the dying task a higher priority"). That commit dramatically improved oom killer logic when a fork-bomb occurs. But I've found that 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. If an admin inserts a !RT process into a cpu cgroup by setting rtruntime=0, usually it runs perfectly because a !RT task isn't affected by the rtruntime knob. But if it promotes an RT task via an explicit setscheduler() syscall or an OOM, the task can't run at all. In short, the oom killer doesn't work at all if admins are using cpu cgroup and don't touch the rtruntime knob. Eventually, kernel may hang up when oom kill occur. I and the original author Luis agreed to disable this logic. Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> Acked-by: Luis Claudio R. Goncalves <lclaudio@uudg.org> Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> Reviewed-by: Minchan Kim <minchan.kim@gmail.com> Acked-by: David Rientjes <rientjes@google.com> Cc: <stable@kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/io-mapping.txt')
0 files changed, 0 insertions, 0 deletions