Linux Manual Pages development
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Alex Yang <himself6565@gmail.com>,
	 linux-man@vger.kernel.org,  Alex Yang <himself65@outlook.com>
Subject: Re: [PATCH] man/man2/getrusage.2: clarify ru_maxrss unit as kibibytes (KiB)
Date: Sun, 17 Aug 2025 23:52:39 -0700	[thread overview]
Message-ID: <87wm71yvd4.fsf@gmail.com> (raw)
In-Reply-To: <iutkhvhpxre54i6a5zt4s3xt6khpmignznhg6wdzue5efbhbhh@hgdvsivvg2km>

[-- Attachment #1: Type: text/plain, Size: 716 bytes --]

Alejandro Colomar <alx@kernel.org> writes:

>> -This is the maximum resident set size used (in kilobytes).
>> +This is the maximum resident set size used (in kibibytes).
>
> Should we maybe say this?
>
> 	(in KiB).

This sounds better to me based on it's use elsewhere:


    $ grep --exclude-dir=.git -rl 'KiB'
    man/man2/ioctl_fsmap.2
    man/man2/process_vm_readv.2
    man/man2/readv.2
    man/man2/alloc_hugepages.2
    man/man3/btree.3
    man/man4/fd.4
    man/man5/proc_kcore.5
    man/man5/proc_sys_vm.5
    man/man7/units.7

Writing out the full name of the IEC unit is much less common:

    $ grep --exclude-dir=.git -rl 'kibi'
    man/man2/msgctl.2
    man/man5/tmpfs.5
    man/man7/units.7


Collin


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2025-08-18  6:52 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 [this message]
2025-08-18  6:58     ` Alejandro Colomar
2025-08-18  7:59       ` [PATCH] man/man2/getrusage.2: clarify ru_maxrss unit as KiB Alex Yang
2025-08-18  9:36         ` 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=87wm71yvd4.fsf@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=alx@kernel.org \
    --cc=himself6565@gmail.com \
    --cc=himself65@outlook.com \
    --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