From: "张元瀚 Tio Zhang" <tiozhang@didiglobal.com>
To: "wang.yaxin@zte.com.cn" <wang.yaxin@zte.com.cn>,
"peterz@infradead.org" <peterz@infradead.org>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"fan.yu9@zte.com.cn" <fan.yu9@zte.com.cn>,
"corbet@lwn.net" <corbet@lwn.net>,
"bsingharora@gmail.com" <bsingharora@gmail.com>,
"yang.yang29@zte.com.cn" <yang.yang29@zte.com.cn>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"juri.lelli@redhat.com" <juri.lelli@redhat.com>,
"vincent.guittot@linaro.org" <vincent.guittot@linaro.org>,
"dietmar.eggemann@arm.com" <dietmar.eggemann@arm.com>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"bsegall@google.com" <bsegall@google.com>,
"mgorman@suse.de" <mgorman@suse.de>,
"vschneid@redhat.com" <vschneid@redhat.com>,
"jiang.kun2@zte.com.cn" <jiang.kun2@zte.com.cn>,
"xu.xin16@zte.com.cn" <xu.xin16@zte.com.cn>,
"zyhtheonly@gmail.com" <zyhtheonly@gmail.com>,
"zyhtheonly@yeah.net" <zyhtheonly@yeah.net>
Subject: Re: [PATCH v3] delayaccy/sched: add SOFTIRQ delay
Date: Tue, 16 Sep 2025 09:12:39 +0000 [thread overview]
Message-ID: <C126DFBF-863E-46AB-BD62-A9E720B3E68F@didiglobal.com> (raw)
In-Reply-To: <20250830142944929e1M6lffs_PwvPfl7J-R1g@zte.com.cn>
>>Intro SOFTIRQ delay, so we can separate softirq as SOFTIRQ delay
>>and hardirq as {IRQ - SOFTIRQ} delay.
>>
>>A typical scenario is when tasks delayed by network,
>>if they delayed by rx net packets, i.e, net_rx_action(),
>>SOFTIRQ delay is almost same as IRQ delay;
>>if they delayed by, e.g, bad driver or broken hardware,
>>SOFTIRQ delay is almost 0 while IRQ delay remains big.
>>
>>Examples tool usage could be found in
>>Documentation/accounting/delay-accounting.rst
>>
>>Signed-off-by: Tio Zhang <tiozhang@didiglobal.com <mailto:tiozhang@didiglobal.com>>
>Reviewed-by: Wang Yaxin <wang.yaxin@zte.com.cn <mailto:wang.yaxin@zte.com.cn>>
>Thanks
>Yaxin
Hi Peter,
Gentle ping. Wondering if you have any further comments?
Thanks for your time.
Best,
Tio Zhang
next prev parent reply other threads:[~2025-09-16 9:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 9:27 [PATCH] delayacct/sched: add SOFTIRQ delay Tio Zhang
2025-08-19 10:14 ` Peter Zijlstra
2025-08-20 8:13 ` Tio Zhang
2025-08-20 8:19 ` [PATCH v2] delayaccy/sched: " Tio Zhang
2025-08-27 3:14 ` wang.yaxin
2025-08-28 9:26 ` [PATCH v3] " Tio Zhang
2025-08-30 6:25 ` wang.yaxin
2025-08-30 6:29 ` wang.yaxin
2025-09-16 9:12 ` 张元瀚 Tio Zhang [this message]
2025-08-20 0:27 ` [PATCH] delayacct/sched: " kernel test robot
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=C126DFBF-863E-46AB-BD62-A9E720B3E68F@didiglobal.com \
--to=tiozhang@didiglobal.com \
--cc=akpm@linux-foundation.org \
--cc=bsegall@google.com \
--cc=bsingharora@gmail.com \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=fan.yu9@zte.com.cn \
--cc=jiang.kun2@zte.com.cn \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=wang.yaxin@zte.com.cn \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
--cc=zyhtheonly@gmail.com \
--cc=zyhtheonly@yeah.net \
/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