From: Jonathan Corbet <corbet@lwn.net>
To: Randy Dunlap <rdunlap@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH] Documentation: /proc/loadavg: add 3 more field descriptions
Date: Thu, 04 Feb 2021 14:35:41 -0700 [thread overview]
Message-ID: <87czxffrde.fsf@meer.lwn.net> (raw)
In-Reply-To: <fe55b139-bd03-4762-199b-83be873cf7dd@infradead.org>
Randy Dunlap <rdunlap@infradead.org> writes:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Update contents of /proc/loadavg: add 3 more fields.
...except that two of those fields are actually a single field with a
slash in the middle.
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: linux-doc@vger.kernel.org
> ---
> Documentation/filesystems/proc.rst | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> --- linux-next-20210202.orig/Documentation/filesystems/proc.rst
> +++ linux-next-20210202/Documentation/filesystems/proc.rst
> @@ -687,7 +687,10 @@ files are there, and which are missing.
> kcore Kernel core image (can be ELF or A.OUT(deprecated in 2.4))
> kmsg Kernel messages
> ksyms Kernel symbol table
> - loadavg Load average of last 1, 5 & 15 minutes
> + loadavg Load average of last 1, 5 & 15 minutes;
> + number of processes currently runnable (running or on ready queue);
> + total number of processes in system;
Given that those two fields (for reasons certainly unknown to me) are
different than the rest, it seems like we should actually explain how
they are formatted.
> + last pid created.
> locks Kernel locks
> meminfo Memory info
> misc Miscellaneous
The patch is an improvement over what's there now, so I've applied it,
but it seems like a further tweak might be called for.
Thanks,
jon
prev parent reply other threads:[~2021-02-04 21:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 3:32 [PATCH] Documentation: /proc/loadavg: add 3 more field descriptions Randy Dunlap
2021-02-04 21:35 ` Jonathan Corbet [this message]
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=87czxffrde.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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