Searched refs:killer (Results 1 – 15 of 15) sorted by relevance
| /Linux-v4.19/Documentation/media/uapi/v4l/ |
| D | vidioc-enuminput.rst | 167 - A color killer circuit automatically disables color decoding when
169 killer is enabled *and* has shut off color decoding.
|
| D | control.rst | 190 Enable the color killer (i. e. force a black & white image in case
|
| D | hist-v4l2.rst | 792 killer is enabled, but also if it is active. (The color killer
|
| /Linux-v4.19/drivers/tty/ |
| D | sysrq.c | 137 char *killer = NULL; in sysrq_handle_crash() local
147 *killer = 1; in sysrq_handle_crash()
|
| /Linux-v4.19/Documentation/sysctl/ |
| D | vm.txt | 271 OOM killer because some writers (e.g. direct block device writes) can
624 score, and name. This is helpful to determine why the OOM killer was
626 the OOM killer chose the task it did to kill.
635 OOM killer actually kills a memory-hogging task.
646 If this is set to zero, the OOM killer will scan through the entire
651 If this is set to non-zero, the OOM killer simply kills the task that
739 may be killed by oom-killer. No panic occurs in this case.
|
| /Linux-v4.19/Documentation/cgroup-v1/ |
| D | memory.txt | 49 - oom-killer disable knob and oom-notifier
413 terminated by the OOM killer. There are several causes for this:
539 there is a swap storage available. This might lead to memcg OOM killer
746 You can disable the OOM-killer by writing "1" to memory.oom_control file, as:
750 If OOM-killer is disabled, tasks under cgroup will hang/sleep
763 oom_kill_disable 0 or 1 (if 1, oom-killer is disabled)
787 about to out of memory (OOM) or even the in-kernel OOM killer is on its
853 (Expect a bunch of notifications, and eventually, the oom-killer will
|
| /Linux-v4.19/Documentation/admin-guide/mm/ |
| D | concepts.rst | 214 OOM killer
219 `OOM killer`. Its mission is simple: all it has to do is to select a
|
| D | ksm.rst | 50 with EAGAIN, but more probably arousing the Out-Of-Memory killer.
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 1014 unprotected reclaimable memory available, OOM killer
1058 Going over the high limit never invokes the OOM killer and
1067 can't be reduced, the OOM killer is invoked in the cgroup.
1080 an indivisible workload by the OOM killer. If set,
1089 If the OOM killer is invoked in a cgroup, it's not going
1123 killer and retrying allocation or failing allocation.
1132 killed by any kind of OOM killer.
1283 Because breach of the high limit doesn't trigger the OOM killer but
2094 limit that can not budge, even if the OOM killer has to be called.
2107 OOM killer. As a result, a high boundary that is chosen too
|
| D | sysrq.rst | 96 ``f`` Will call the oom killer to kill a memory hog process, but do not
|
| /Linux-v4.19/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
1475 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1491 The amount of "allowed" memory depends on the context in which the oom killer
1526 Caveat: when a parent task is selected, the oom killer will sacrifice any first
1532 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1535 This file can be used to check the current score used by the oom-killer is for
|
| /Linux-v4.19/Documentation/ |
| D | robust-futexes.txt | 68 The second disadvantage is a real killer: pthread_exit() takes around 1
|
| /Linux-v4.19/Documentation/vm/ |
| D | hmm.rst | 368 A drawback is that the OOM killer might kill an application using a lot of
|
| /Linux-v4.19/Documentation/filesystems/ext4/ |
| D | ext4.rst | 356 provoke the Out Of Memory killer. (For example,
|
| /Linux-v4.19/mm/ |
| D | Kconfig | 240 the lack of the feature can lead to unexpected OOM killer
|
