From: Markus Elfring <Markus.Elfring@web.de>
To: Fan Yu <fan.yu9@zte.com.cn>, Jiang Kun <jiang.kun2@zte.com.cn>,
Wang Yaxin <wang.yaxin@zte.com.cn>,
linux-mm@kvack.org
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-doc@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <bsingharora@gmail.com>,
David Hildenbrand <david@redhat.com>,
Peilin He <he.peilin@zte.com.cn>,
tu.qiang35@zte.com.cn, Wang Yong <wang.yong12@zte.com.cn>,
xu xin <xu.xin16@zte.com.cn>, Yang Yang <yang.yang29@zte.com.cn>,
Yunkai Zhang <zhang.yunkai@zte.com.cn>,
Yutan Qiu <qiu.yutan@zte.com.cn>
Subject: Re: [PATCH linux next] delaytop: add psi info to show system delay
Date: Sat, 12 Jul 2025 19:33:31 +0200 [thread overview]
Message-ID: <6a4de937-f433-41c9-9c28-2f46070a3cbe@web.de> (raw)
In-Reply-To: <20250710135451340_5pOgpIFi0M5AE7H44W1D@zte.com.cn>
> support showing whole delay of system by reading PSI,
> just like the first few lines of information output
> by the top command. the output of delaytop includes
…
You may occasionally put more than 53 characters into text lines
of such a change description.
…
> +++ b/tools/accounting/delaytop.c
…
> @@ -549,7 +659,29 @@ static void display_results(void)
> FILE *out = stdout;
>
> fprintf(out, "\033[H\033[J");
> -
> + /* PSI output (one-line, no cat style) */
> + fprintf(out, "System Pressure Information: ");
> + fprintf(out, "(avg10/avg60/avg300/total)\n");
> + fprintf(out, "CPU:");
…
Under which circumstances would you care more also for file output failures?
https://cwe.mitre.org/data/definitions/252.html
Regards,
Markus
prev parent reply other threads:[~2025-07-12 17:33 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
2025-07-12 17:33 ` Markus Elfring [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=6a4de937-f433-41c9-9c28-2f46070a3cbe@web.de \
--to=markus.elfring@web.de \
--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=yang.yang29@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