Searched refs:killer (Results 1 – 8 of 8) sorted by relevance
3 Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's16 introduced with the oom killer rewrite that allows users to increase or
130 char *killer = NULL; in sysrq_handle_crash() local134 *killer = 1; in sysrq_handle_crash()
506 name. This is helpful to determine why the OOM killer was invoked516 OOM killer actually kills a memory-hogging task.527 If this is set to zero, the OOM killer will scan through the entire532 If this is set to non-zero, the OOM killer simply kills the task that600 may be killed by oom-killer. No panic occurs in this case.
31 probably arousing the Out-Of-Memory killer.
44 - oom-killer disable knob and oom-notifier324 terminated by OOM killer. There are several causes for this:633 You can disable OOM-killer by writing "1" to memory.oom_control file, as:638 If OOM-killer is disabled, tasks under cgroup will hang/sleep651 oom_kill_disable 0 or 1 (if 1, oom-killer is disabled)
36 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the oom-killer38 3.2 /proc/<pid>/oom_score - Display current oom-killer score1276 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score1292 The amount of "allowed" memory depends on the context in which the oom killer1333 Caveat: when a parent task is selected, the oom killer will sacrifice any first1339 3.2 /proc/<pid>/oom_score - Display current oom-killer score1342 This file can be used to check the current score used by the oom-killer is for
148 Why: /proc/<pid>/oom_adj allows userspace to influence the oom killer's161 introduced with the oom killer rewrite that allows users to increase or
64 The second disadvantage is a real killer: pthread_exit() takes around 1