Searched refs:killer (Results 1 – 8 of 8) sorted by relevance
| /linux-4.1.27/drivers/tty/ |
| D | sysrq.c | 134 char *killer = NULL; in sysrq_handle_crash() local
138 *killer = 1; in sysrq_handle_crash()
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | memory.txt | 49 - oom-killer disable knob and oom-notifier
421 terminated by the OOM killer. There are several causes for this:
546 there is a swap storage available. This might lead to memcg OOM killer
753 You can disable the OOM-killer by writing "1" to memory.oom_control file, as:
757 If OOM-killer is disabled, tasks under cgroup will hang/sleep
770 oom_kill_disable 0 or 1 (if 1, oom-killer is disabled)
794 about to out of memory (OOM) or even the in-kernel OOM killer is on its
837 (Expect a bunch of notifications, and eventually, the oom-killer will
|
| D | unified-hierarchy.txt | 358 limit that can not budge, even if the OOM killer has to be called.
371 OOM killer. As a result, a high boundary that is chosen too
|
| /linux-4.1.27/Documentation/sysctl/ |
| D | vm.txt | 572 score, and name. This is helpful to determine why the OOM killer was
574 the OOM killer chose the task it did to kill.
583 OOM killer actually kills a memory-hogging task.
594 If this is set to zero, the OOM killer will scan through the entire
599 If this is set to non-zero, the OOM killer simply kills the task that
687 may be killed by oom-killer. No panic occurs in this case.
|
| /linux-4.1.27/Documentation/vm/ |
| D | ksm.txt | 31 probably arousing the Out-Of-Memory killer.
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | proc.txt | 36 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the oom-killer
38 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1422 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1438 The amount of "allowed" memory depends on the context in which the oom killer
1473 Caveat: when a parent task is selected, the oom killer will sacrifice any first
1479 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1482 This file can be used to check the current score used by the oom-killer is for
|
| D | ext4.txt | 382 provoke the Out Of Memory killer. (For example,
|
| /linux-4.1.27/Documentation/ |
| D | robust-futexes.txt | 64 The second disadvantage is a real killer: pthread_exit() takes around 1
|