From: Andrew Morton <akpm@linux-foundation.org>
To: <wang.yaxin@zte.com.cn>
Cc: <fan.yu9@zte.com.cn>, <yang.yang29@zte.com.cn>, <corbet@lwn.net>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<xu.xin16@zte.com.cn>
Subject: Re: [PATCH 0/3 v3] delaytop: add delay max, timestamp and sorting for top latency analysis
Date: Thu, 2 Jul 2026 16:01:52 -0700 [thread overview]
Message-ID: <20260702160152.ab0a3dea97e06652cf4874ac@linux-foundation.org> (raw)
In-Reply-To: <20260702205704180NZ3cu_QF04KfBIL6vjTHL@zte.com.cn>
On Thu, 2 Jul 2026 20:57:04 +0800 (CST) <wang.yaxin@zte.com.cn> wrote:
> Previously delaytop only showed average delays. This patch adds:
>
> 1. delay_max fields to track the maximum delay value for each delay type
> (cpu, blkio, irq, swapin, freepages, thrashing, compact, wpcopy)
> per task.
>
> 2. The -t/--type option displays only the specified delay type with avg/max
> values side by side, allowing focused analysis:
> delaytop -t cpu # Show only CPU delay with avg/max
> delaytop -t wpcopy # Show Copy-on-Write delay with avg/max
>
> 3. Wall-clock timestamp when each maximum delay occurred, displayed in the
> MAX_TIMESTAMP column when using -t/--type option. This enables:
> - Identifying the time when a process experienced an abnormal delay max
> - Correlating delay max across multiple processes at the same timestamp
> - Cross-referencing with logs, traces, or other metrics at that time
>
> 4. When using -t/--type option, tasks are sorted by maximum delay value in
> descending order (largest delay first), enabling quick identification of
> top N processes with highest delay spikes.
Seems useful, thanks - I'll queue this for testing.
AI review might have found a couple of things:
https://sashiko.dev/#/patchset/20260702205704180NZ3cu_QF04KfBIL6vjTHL@zte.com.cn
prev parent reply other threads:[~2026-07-02 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 12:57 [PATCH 0/3 v3] delaytop: add delay max, timestamp and sorting for top latency analysis wang.yaxin
2026-07-02 12:58 ` [PATCH 1/3] delaytop: add delay max for delaytop wang.yaxin
2026-07-02 22:58 ` Andrew Morton
2026-07-02 12:58 ` [PATCH 2/3] delaytop: add timestamp of delay max wang.yaxin
2026-07-02 23:01 ` Andrew Morton
2026-07-02 13:00 ` [PATCH 3/3] delaytop: sort by max delay to highlight top latency processes wang.yaxin
2026-07-02 23:01 ` Andrew Morton [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=20260702160152.ab0a3dea97e06652cf4874ac@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=fan.yu9@zte.com.cn \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wang.yaxin@zte.com.cn \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@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