From: "David Wang" <00107082@163.com>
To: linux-kernel@vger.kernel.org
Subject: [/proc/vmstat] nr_kernel_stack is actually meminfo_kernel_stack_kb? why...
Date: Tue, 27 Dec 2022 20:09:11 +0800 (CST) [thread overview]
Message-ID: <66e657e6.38d5.185537c93f0.Coremail.00107082@163.com> (raw)
Hi,
The nr_kernel_stack in /proc/vmstat now is the same as KernelStack /proc/meminfo, and has been this way since a change made six years ago (https://lore.kernel.org/lkml/24279d4009c821de64109055665429fad2a7bff7.1466036668.git.luto@kernel.org/)
The situation now is very confusing:
1. the naming should be changed, how could one take 'nr_kernel_stack' as a naming for meminfo-KernelStack-KB?
2. Dose kernel.threads-max now means kernel.threads-max-kB?
3. I really think the number of threads currently running in the system is a very usful stastistic, I used to collect nr_kernel_stack in /proc/vmstat to monitor thread/task usage in the system, and trigger alarm when nr_kernel_stack is approaching somewhere near kernel.threads-max.
Hope things can be changed, and nr_kernel_stack could be restored/fixed to its old meaning.
David
reply other threads:[~2022-12-27 12:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=66e657e6.38d5.185537c93f0.Coremail.00107082@163.com \
--to=00107082@163.com \
--cc=linux-kernel@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