linux-kernel - Re: [PATCH linux-next 1/3] tools/delaytop: add memory verbose mode support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250904111546690OmuebcWPO9GlbF9QC7wgA@zte.com.cn>
Date: Thu, 4 Sep 2025 11:15:46 +0800 (CST)
From: <fan.yu9@....com.cn>
To: <xu.xin16@....com.cn>
Cc: <akpm@...ux-foundation.org>, <wang.yaxin@....com.cn>,
        <linux-kernel@...r.kernel.org>, <linux-doc@...r.kernel.org>,
        <yang.yang29@....com.cn>
Subject: Re: [PATCH linux-next 1/3] tools/delaytop: add memory verbose mode support

> This feature is very useful to analyze specific delay sources due to memory operations.
> 
> But these shown datas are basically average values rather than min/max, it's not enough
> 
> for debugging delay jitters. Will you add showing min/max values to delaytop in future? 

Hi Xu,
Thanks for the review and the great suggestions!
You’re right, averages alone aren’t enough for diagnosing the sources of delay jitter.
I will work on adding min/max support in the next version.

> I think if users press 'M', delaytop doesn't need to shown CPU/IRQ/IO delays, just show the detailed memory delays.

Good point. When ‘M’ is pressed, the user wants to focus on memory. Showing CPU/IRQ/IO is just noise.
I’ll change the behavior in the next version so that ‘M’ switches to a clean, memory-only view.

Best regards,
Fan Yu