linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: <jiang.kun2@zte.com.cn>
Cc: <bsingharora@gmail.com>, <david@redhat.com>,
	<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
	<linux-doc@vger.kernel.org>, <wang.yong12@zte.com.cn>,
	<wang.yaxin@zte.com.cn>, <fan.yu9@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>,
	<yang.yang29@zte.com.cn>
Subject: Re: [PATCH linux next] delayacct: add delay max to record delay peak
Date: Tue, 3 Dec 2024 17:08:16 -0800	[thread overview]
Message-ID: <20241203170816.3fe81941fe1866ca1672eba8@linux-foundation.org> (raw)
In-Reply-To: <20241203164848805CS62CQPQWG9GLdQj2_BxS@zte.com.cn>

On Tue, 3 Dec 2024 16:48:48 +0800 (CST) <jiang.kun2@zte.com.cn> wrote:

> From: Wang Yaxin <wang.yaxin@zte.com.cn>
> 
> Introduce the use cases of delay max, which can help quickly detect
> potential abnormal delays in the system and record the types and
> specific details of delay spikes.
>   
> Problem
> ========
> Delay accounting can track the average delay of processes to show
> system workload. However, when a process experiences a significant
> delay, maybe a delay spike, which adversely affects performance,
> getdelays can only display the average system delay over a period
> of time. Yet, average delay is unhelpful for diagnosing delay peak.
> It is not even possible to determine which type of delay has spiked,
> as this information might be masked by the average delay.
> 
> Solution
> =========
> the 'delay max' can display delay peak since the system's startup,
> which can record potential abnormal delays over time, including
> the type of delay and the maximum delay. This is helpful for
> quickly identifying crash caused by delay.

Seems sensible, and the implementation is straightforward.  I'll queue
it for testing and review.

>  include/linux/delayacct.h      |  7 ++++
>  include/linux/sched.h          |  3 ++
>  include/uapi/linux/taskstats.h |  9 ++++++
>  kernel/delayacct.c             | 35 ++++++++++++++------
>  kernel/sched/stats.h           |  5 ++-
>  tools/accounting/getdelays.c   | 59 ++++++++++++++++++++--------------

Please prepare a v2 which includes an update to
Documentation/accounting/delay-accounting.rst.

> 
> ...
>
> --- a/kernel/delayacct.c
> +++ b/kernel/delayacct.c
> @@ -95,7 +95,7 @@ void __delayacct_tsk_init(struct task_struct *tsk)
>   * Finish delay accounting for a statistic using its timestamps (@start),
>   * accumalator (@total) and @count

And I wouldn't be offended if v2 fixed that spelling error!  "accumulator".




  reply	other threads:[~2024-12-04  1:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03  8:48 jiang.kun2
2024-12-04  1:08 ` Andrew Morton [this message]
2024-12-04  1:43   ` yang.yang29
2024-12-05 11:10 yaxin_wang

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=20241203170816.3fe81941fe1866ca1672eba8@linux-foundation.org \
    --to=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=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