From: Guillem Jover <guillem@hadrons.org>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: [PATCH 3/4] proc.5: Document that /proc/<pid>/oom_adj is no longer present
Date: Mon, 17 Apr 2023 01:35:51 +0200 [thread overview]
Message-ID: <20230416233552.283776-4-guillem@hadrons.org> (raw)
In-Reply-To: <20230416233552.283776-1-guillem@hadrons.org>
Signed-off-by: Guillem Jover <guillem@hadrons.org>
---
man5/proc.5 | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/man5/proc.5 b/man5/proc.5
index 4bb7dd262..a3b5ffc7b 100644
--- a/man5/proc.5
+++ b/man5/proc.5
@@ -1640,7 +1640,9 @@ although a process can always increase its own
setting (since 2.6.20).
.IP
Since Linux 2.6.36, use of this file is deprecated in favor of
-.IR /proc/ pid /oom_score_adj .
+.IR /proc/ pid /oom_score_adj ,
+.\" commit 01dc52ebdf472f77cca623ca693ca24cfc0f1bbe
+and finally removed in Linux 3.7.
.TP
.IR /proc/ pid /oom_score " (since Linux 2.6.11)"
.\" See mm/oom_kill.c::badness() before Linux 2.6.36 sources
--
2.40.0
next prev parent reply other threads:[~2023-04-16 23:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-16 23:35 [PATCH 0/4] proc.5: Fixes and updates Guillem Jover
2023-04-16 23:35 ` [PATCH 1/4] proc.5: Document exact /proc/PID/exe behavior on unlinked pathnames Guillem Jover
2023-04-17 18:18 ` Alejandro Colomar
2023-04-16 23:35 ` [PATCH 2/4] proc.5: A process can increase its own /proc/PID/oom_adj setting Guillem Jover
2023-04-17 18:20 ` Alejandro Colomar
2023-04-16 23:35 ` Guillem Jover [this message]
2023-04-17 18:28 ` [PATCH 3/4] proc.5: Document that /proc/<pid>/oom_adj is no longer present Alejandro Colomar
2023-04-16 23:35 ` [PATCH 4/4] proc.5: tfix Guillem Jover
2023-04-17 18:29 ` Alejandro Colomar
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=20230416233552.283776-4-guillem@hadrons.org \
--to=guillem@hadrons.org \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
/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).