Home
last modified time | relevance | path

Searched refs:oom_score_adj (Results 1 – 11 of 11) sorted by relevance

/Linux-v5.4/include/trace/events/
Dtask.h19 __field( short, oom_score_adj)
26 __entry->oom_score_adj = task->signal->oom_score_adj;
31 __entry->clone_flags, __entry->oom_score_adj)
44 __field( short, oom_score_adj)
51 __entry->oom_score_adj = task->signal->oom_score_adj;
56 __entry->newcomm, __entry->oom_score_adj)
Doom.h19 __field( short, oom_score_adj)
25 __entry->oom_score_adj = task->signal->oom_score_adj;
29 __entry->pid, __entry->comm, __entry->oom_score_adj)
/Linux-v5.4/samples/bpf/
Dtest_overhead_kprobe_kern.c21 u16 oom_score_adj; in prog() local
30 oom_score_adj = _(signal->oom_score_adj); in prog()
Dtest_overhead_tp_kern.c16 __u16 oom_score_adj; member
/Linux-v5.4/mm/
Doom_kill.c215 adj = (long)p->signal->oom_score_adj; in oom_badness()
407 task->signal->oom_score_adj, task->comm); in dump_task()
456 current->signal->oom_score_adj); in dump_header()
893 mm_pgtables_bytes(mm), victim->signal->oom_score_adj); in __oom_kill_process()
943 if (task->signal->oom_score_adj != OOM_SCORE_ADJ_MIN && in oom_kill_memcg_member()
1090 current->signal->oom_score_adj != OOM_SCORE_ADJ_MIN) { in out_of_memory()
/Linux-v5.4/fs/proc/
Dbase.c1027 if (task->signal->oom_score_adj == OOM_SCORE_ADJ_MAX) in oom_adj_read()
1030 oom_adj = (task->signal->oom_score_adj * -OOM_DISABLE) / in oom_adj_read()
1050 if (oom_adj < task->signal->oom_score_adj && in __set_oom_adj()
1087 task->signal->oom_score_adj = oom_adj; in __set_oom_adj()
1106 p->signal->oom_score_adj = oom_adj; in __set_oom_adj()
1180 short oom_score_adj = OOM_SCORE_ADJ_MIN; in oom_score_adj_read() local
1185 oom_score_adj = task->signal->oom_score_adj; in oom_score_adj_read()
1187 len = snprintf(buffer, sizeof(buffer), "%hd\n", oom_score_adj); in oom_score_adj_read()
1195 int oom_score_adj; in oom_score_adj_write() local
1206 err = kstrtoint(strstrip(buffer), 0, &oom_score_adj); in oom_score_adj_write()
[all …]
/Linux-v5.4/include/linux/sched/
Dsignal.h219 short oom_score_adj; /* OOM kill score adjustment */ member
/Linux-v5.4/Documentation/filesystems/
Dproc.txt36 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the oom-killer
1520 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1545 The value of /proc/<pid>/oom_score_adj is added to the badness score before it
1554 consider for each task. Setting a /proc/<pid>/oom_score_adj value of +500, for
1565 scaled linearly with /proc/<pid>/oom_score_adj.
1567 The value of /proc/<pid>/oom_score_adj may be reduced no lower than the last
1581 any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which
/Linux-v5.4/kernel/
Dfork.c1589 sig->oom_score_adj = current->signal->oom_score_adj; in copy_signal()
/Linux-v5.4/Documentation/admin-guide/sysctl/
Dvm.rst640 pid, uid, tgid, vm size, rss, pgtables_bytes, swapents, oom_score_adj
/Linux-v5.4/Documentation/admin-guide/
Dcgroup-v2.rst1176 Tasks with the OOM protection (oom_score_adj set to -1000)