From: Michal Hocko <mhocko@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>
Cc: David Rientjes <rientjes@google.com>,
Yafang Shao <laoar.shao@gmail.com>, <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.com>
Subject: [PATCH 2/2] doc, mm: clarify /proc/<pid>/oom_score value range
Date: Thu, 9 Jul 2020 08:26:03 +0200 [thread overview]
Message-ID: <20200709062603.18480-2-mhocko@kernel.org> (raw)
In-Reply-To: <20200709062603.18480-1-mhocko@kernel.org>
From: Michal Hocko <mhocko@suse.com>
The exported value includes oom_score_adj so the range is no [0, 1000]
as described in the previous section but rather [0, 2000]. Mention that
fact explicitly.
Signed-off-by: Michal Hocko <mhocko@suse.com>
---
Documentation/filesystems/proc.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/filesystems/proc.rst b/Documentation/filesystems/proc.rst
index 8e3b5dffcfa8..78a0dec323a3 100644
--- a/Documentation/filesystems/proc.rst
+++ b/Documentation/filesystems/proc.rst
@@ -1673,6 +1673,9 @@ requires CAP_SYS_RESOURCE.
3.2 /proc/<pid>/oom_score - Display current oom-killer score
-------------------------------------------------------------
+Please note that the exported value includes oom_score_adj so it is effectively
+in range [0,2000].
+
This file can be used to check the current score used by the oom-killer is for
any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which
process should be killed in an out-of-memory situation.
--
2.27.0
next prev parent reply other threads:[~2020-07-09 6:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 6:26 [PATCH 1/2] doc, mm: sync up oom_score_adj documentation Michal Hocko
2020-07-09 6:26 ` Michal Hocko [this message]
2020-07-09 7:41 ` [PATCH 2/2] doc, mm: clarify /proc/<pid>/oom_score value range Yafang Shao
2020-07-09 8:18 ` Michal Hocko
2020-07-09 9:01 ` Yafang Shao
2020-07-09 9:58 ` Michal Hocko
2020-07-09 11:20 ` Yafang Shao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200709062603.18480-2-mhocko@kernel.org \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).