1 .\" Copyright (C) 1994, 1995, Daniel Quinlan <quinlan@yggdrasil.com>
2 .\" Copyright (C) 2002-2008, 2017, Michael Kerrisk <mtk.manpages@gmail.com>
3 .\" Copyright (C) 2023, Alejandro Colomar <alx@kernel.org>
5 .\" SPDX-License-Identifier: GPL-3.0-or-later
7 .TH proc_pid_oom_score 5 (date) "Linux man-pages (unreleased)"
9 /proc/pid/oom_score \- OOM-killer score
12 .IR /proc/ pid /oom_score " (since Linux 2.6.11)"
13 .\" See mm/oom_kill.c::badness() before Linux 2.6.36 sources
14 .\" See mm/oom_kill.c::oom_badness() after Linux 2.6.36
15 .\" commit a63d83f427fbce97a6cea0db2e64b0eb8435cd10
16 This file displays the current score that the kernel gives to
17 this process for the purpose of selecting a process
19 A higher score means that the process is more likely to be
20 selected by the OOM-killer.
21 The basis for this score is the amount of memory used by the process,
22 with increases (+) or decreases (\-) for factors including:
23 .\" See mm/oom_kill.c::badness() before Linux 2.6.36 sources
24 .\" See mm/oom_kill.c::oom_badness() after Linux 2.6.36
25 .\" commit a63d83f427fbce97a6cea0db2e64b0eb8435cd10
28 whether the process is privileged (\-).
29 .\" More precisely, if it has CAP_SYS_ADMIN or (pre 2.6.36) CAP_SYS_RESOURCE
33 the following factors were also used in the calculation of oom_score:
36 whether the process creates a lot of children using
40 whether the process has been running a long time,
41 or has used a lot of CPU time (\-);
43 whether the process has a low nice value (i.e., > 0) (+); and
45 whether the process is making direct hardware access (\-).
46 .\" More precisely, if it has CAP_SYS_RAWIO
51 also reflects the adjustment specified by the
55 setting for the process.
58 .BR proc_pid_oom_score_adj (5)