Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alex Yang <himself65@outlook.com>
To: alx@kernel.org
Cc: linux-man@vger.kernel.org, Alex Yang <himself65@outlook.com>
Subject: [PATCH] man/man2/getrusage.2: clarify ru_maxrss unit as KiB
Date: Mon, 18 Aug 2025 00:59:05 -0700	[thread overview]
Message-ID: <20250818075905.40146-1-himself65@outlook.com> (raw)
In-Reply-To: <jclco3uxvj7drormblgik6fsa36aemanyxqaf44mhaqgbwszye@nuhauaulbrlg>

The ru_maxrss field was previously documented as using "kilobytes" as its unit. However, the value is actually in multiples of 1024 bytes, which is correctly referred to as "kibibytes" (KiB) according to the IEC standard. This change updates the documentation to use the precise term.
---
 man/man2/getrusage.2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man/man2/getrusage.2 b/man/man2/getrusage.2
index 34e81f540..a1b30e5b5 100644
--- a/man/man2/getrusage.2
+++ b/man/man2/getrusage.2
@@ -88,7 +88,7 @@ expressed in a
 structure (seconds plus microseconds).
 .TP
 .IR ru_maxrss " (since Linux 2.6.32)"
-This is the maximum resident set size used (in kilobytes).
+This is the maximum resident set size used (in KiB).
 For
 .BR RUSAGE_CHILDREN ,
 this is the resident set size of the largest child, not the maximum
-- 
2.50.1


  reply	other threads:[~2025-08-18  7:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18  6:12 [PATCH] man/man2/getrusage.2: clarify ru_maxrss unit as kibibytes (KiB) Your Name
2025-08-18  6:30 ` Alejandro Colomar
2025-08-18  6:52   ` Collin Funk
2025-08-18  6:58     ` Alejandro Colomar
2025-08-18  7:59       ` Alex Yang [this message]
2025-08-18  9:36         ` [PATCH] man/man2/getrusage.2: clarify ru_maxrss unit as KiB Alejandro Colomar
2025-08-18  8:19       ` Alex Yang

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=20250818075905.40146-1-himself65@outlook.com \
    --to=himself65@outlook.com \
    --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