From: ningle <ning.le@h3c.com>
To: <corbet@lwn.net>
Cc: <linux-doc@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <ning.le@h3c.com>,
<zhang.chunA@h3c.com>
Subject: Re: [PATCH] proc/stat: document uptime-based CPU utilization calculation
Date: Tue, 20 Jan 2026 15:20:18 +0800 [thread overview]
Message-ID: <20260120072018.3139470-1-ning.le@h3c.com> (raw)
In-Reply-To: <20251226043409.1063711-1-ning.le@h3c.com>
Hi,
Gentle ping on this documentation patch.
The main motivation is to describe how userspace can compute more stable
CPU utilization on systems that already enable NOHZ and virtual CPU
accounting (CONFIG_VIRT_CPU_ACCOUNTING_*), where idle time in /proc/stat
is already accurate.
In this context, improving observability is often easier by providing a
better time reference for these existing counters (e.g. a timestamp
field in /proc/stat), rather than enabling additional options like
CONFIG_CONTEXT_TRACKING_USER_FORCE, which may be too heavy for many
production environments.
If this direction is acceptable, I can adjust the text or placement as
you prefer.
Thanks,
ning le
prev parent reply other threads:[~2026-01-20 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 4:34 [PATCH] Subject: [PATCH] proc/stat: document uptime-based CPU utilization calculation ningle
2026-01-20 7:20 ` ningle [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=20260120072018.3139470-1-ning.le@h3c.com \
--to=ning.le@h3c.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhang.chunA@h3c.com \
/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