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>, <ye.xingchen@zte.com.cn>,
<xu.xin16@zte.com.cn>, <jiang.kun2@zte.com.cn>
Subject: Re: [PATCH linux next] tools/accounting/delaytop: add delaytop
to record top-n task delay
Date: Tue, 24 Jun 2025 10:18:35 +0800 (CST) [thread overview]
Message-ID: <20250624101835869AZSKLr2_kXapp5khYIQ7H@zte.com.cn> (raw)
In-Reply-To: <20250619225152603EIiJTlhHy4mFMv1dVTzue@zte.com.cn>
> For latency-sensitive scenarios, such as industrial control, communications,
> or automotive, I think this tool is useful. And it may be better if it support
> showing whole delay of system by reading PSI, just like the first few lines of
> information output by the top command.
Another suggestion, we can provide a new command to control the display of
either the total memory delay for tasks or detailed memory delays. This approach
offers two benefits: first, it better aligns with PSI results; second, it offers choices
for users with different interests (e.g., some users may not have enabled or are
not concerned about swap delay). The implementation can follow the dynamic
command approach similar to top.
If it's OK to you, may send follow-up patch. For the initial patch:
> + * delaytop.c - task delay monitoring tool.
> + * This tool provides real-time monitoring and statistics of
> + * system, container, and task-level delays, including CPU,
Since the tool cover 'system' delay, we may say:
delaytop.c - system-wide delay monitoring tool.
> + * This tool provides real-time monitoring and statistics of
> + * system, container, and task-level delays, including CPU,
> + * memory, IO, and IRQ and delay accounting. It supports both
I am confused with the words 'and delay accouting', they are all
delays.
> + if (bind(fd, (struct sockaddr *) &local, sizeof(local)) < 0) {
> + close(fd);
> + return -1;
We better tell user what happend, and pelase check other code
that may also fail.
> + rc = recv(nl_sd, &resp, sizeof(resp), 0);
Please check if close(nl_sd) is called.
next prev parent reply other threads:[~2025-06-24 2:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 13:18 jiang.kun2
2025-06-19 14:51 ` yang.yang29
2025-06-24 2:18 ` yang.yang29 [this message]
2025-06-22 22:48 ` Andrew Morton
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=20250624101835869AZSKLr2_kXapp5khYIQ7H@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=ye.xingchen@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