Skip to contentSkip to conversation

New: oom_adj and oom_score are undocumented

Bug 19382 bugzilla-daemon-590EEB7GvNiWaY/[email protected] 1 participant 5 messages Sep 30, 2010 1 message not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=19382

Summary: oom_adj and oom_score are undocumented
Product: Documentation
Version: unspecified
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
AssignedTo: documentation_man-pages-ztI5WcYan/[email protected]
ReportedBy: landijk-user-/[email protected]
Regression: No

There does not appear to be any kernel documentation on oom_adj and oom_score, which may be set for individual processes to tune the OOM killer. I am not a kernel developer, but below is my suggestion for possible content. It is based on (but not copied from) Red Hat's documentation at
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Deployment_Guide/s2-proc-pid.html.

--

Each process in the /proc tree has two nodes called "oom_adj" and "oom_score." These are related to the operation of the "OOM killer," which is the kernel's tool for resolving situations in which memory has been overcommitted. For more information about memory overcommitment, see the kernel documentation files vm/overcommit-accounting and sysctl/vm.txt.

The oom_score node contains a read-only value indicating the priority associated with the process should an overcommitted situation arise. Lower priority means the process is less likely to be killed, and the lowest possible score is 0.

The oom_adj node is read-write, and its value is used in the computation of the oom_score. Specifically, it is a value in the range -17 to +15, and it is interpreted as a bit shift in the last step of computing the oom_score. Negative values reduce the score, and positive values increase the score. The value -17 is treated specially; it always reduces the oom_score to 0.

--

I am not sure where the documentation should go. Perhaps the OOM killer should have its own page to treat the above topics, as well as the badness() function.

Signature · 7 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): bug-19382-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/

#2 lore raw

[Bug 19382] oom_adj and oom_score are undocumented

https://bugzilla.kernel.org/show_bug.cgi?id=19382

landijk-user-/[email protected] changed:

What |Removed |Added
----------------------------------------------------------------------------

             Blocks|                            |19332
Signature · 7 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#3 lore raw

[Bug 19382] oom_adj and oom_score are undocumented

In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=19382

Randy Dunlap <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from Randy Dunlap <[email protected]> 2010-09-30 18:43:13 --- Documentation/filesystems/proc.txt contains some info in these 2 sections:

3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the
oom-killer
score
3.2 /proc/<pid>/oom_score - Display current oom-killer score

Are these correct or do they need to be updated? If they need to be updated, please send patches against this file.

Signature · 7 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#4 lore raw

[Bug 19382] oom_adj and oom_score are undocumented

In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=19382

landijk-user-/[email protected] changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #2 from landijk-user-/[email protected] 2010-09-30 18:57:21 --- You are right. I have no idea how I missed it.

Signature · 7 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#5 lore raw

[Bug 19382] oom_adj and oom_score are undocumented

In reply to a message not in the archive

https://bugzilla.kernel.org/show_bug.cgi?id=19382

Randy Dunlap <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|RESOLVED                    |CLOSED
         Resolution|INVALID                     |DOCUMENTED
Signature · 7 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html