From: <yang.yang29@zte.com.cn>
To: <wang.yaxin@zte.com.cn>, <fan.yu9@zte.com.cn>
Cc: <bsingharora@gmail.com>, <akpm@linux-foundation.org>,
<david@redhat.com>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <linux-doc@vger.kernel.org>,
<wang.yong12@zte.com.cn>, <he.peilin@zte.com.cn>,
<tu.qiang35@zte.com.cn>, <qiu.yutan@zte.com.cn>,
<zhang.yunkai@zte.com.cn>, <xu.xin16@zte.com.cn>,
<jiang.kun2@zte.com.cn>
Subject: Re: [PATCH linux next] delaytop: add psi info to show system delay
Date: Sun, 13 Jul 2025 00:19:42 +0800 (CST) [thread overview]
Message-ID: <20250713001942027bne2UhpkDuiSVPMxA3LZj@zte.com.cn> (raw)
In-Reply-To: <20250710135451340_5pOgpIFi0M5AE7H44W1D@zte.com.cn>
> bash# ./delaytop
> System Pressure Information: (avg10/avg60/avg300/total)
> CPU: full: 0.0%/ 0.0%/ 0.0%/0 some: 0.1%/ 0.0%/ 0.0%/14216596
> Memory: full: 0.0%/ 0.0%/ 0.0%/34010659 some: 0.0%/ 0.0%/ 0.0%/35406492
> IO: full: 0.1%/ 0.0%/ 0.0%/51029453 some: 0.1%/ 0.0%/ 0.0%/55330465
> IRQ: full: 0.0%/ 0.0%/ 0.0%/0
I see the unit of PSI and task delay are different, they are microseconds
and milliseconds. We'd better keep the units aligned for better user
understanding.
And what about split the output of each delay into different lines just as
PSI, this help us to better compare the results of some and full.
bash# cat /proc/pressure/cpu
some avg10=0.00 avg60=0.00 avg300=0.00 total=682581546
full avg10=0.00 avg60=0.00 avg300=0.00 total=0
For example:
bash# ./delaytop
System Pressure Information: (avg10/avg60/avg300/total)
CPU some: 0.1%/ 0.0%/ 0.0%/14216596
CPU full: 0.0%/ 0.0%/ 0.0%/0
Memory some: 0.0%/ 0.0%/ 0.0%/35406492
Memory full: 0.0%/ 0.0%/ 0.0%/34010659
next prev parent reply other threads:[~2025-07-12 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 5:54 jiang.kun2
2025-07-12 16:19 ` yang.yang29 [this message]
2025-07-12 17:33 ` Markus Elfring
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=20250713001942027bne2UhpkDuiSVPMxA3LZj@zte.com.cn \
--to=yang.yang29@zte.com.cn \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=david@redhat.com \
--cc=fan.yu9@zte.com.cn \
--cc=he.peilin@zte.com.cn \
--cc=jiang.kun2@zte.com.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiu.yutan@zte.com.cn \
--cc=tu.qiang35@zte.com.cn \
--cc=wang.yaxin@zte.com.cn \
--cc=wang.yong12@zte.com.cn \
--cc=xu.xin16@zte.com.cn \
--cc=zhang.yunkai@zte.com.cn \
/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