[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250830142519085d4aXePTT_pSZ3UTxxNC8X@zte.com.cn>
Date: Sat, 30 Aug 2025 14:25:19 +0800 (CST)
From: <wang.yaxin@....com.cn>
To: <tiozhang@...iglobal.com>
Cc: <akpm@...ux-foundation.org>, <fan.yu9@....com.cn>, <corbet@....net>,
<bsingharora@...il.com>, <yang.yang29@....com.cn>,
<linux-kernel@...r.kernel.org>, <linux-doc@...r.kernel.org>,
<mingo@...hat.com>, <peterz@...radead.org>, <juri.lelli@...hat.com>,
<vincent.guittot@...aro.org>, <dietmar.eggemann@....com>,
<rostedt@...dmis.org>, <bsegall@...gle.com>, <mgorman@...e.de>,
<vschneid@...hat.com>, <jiang.kun2@....com.cn>, <xu.xin16@....com.cn>,
<tiozhang@...iglobal.com>, <zyhtheonly@...il.com>,
<zyhtheonly@...h.net>
Subject: Re: [PATCH v3] delayaccy/sched: add SOFTIRQ delay
>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@...iglobal.com>
>---
a small suggestion: it would be clearer if you could include a changelog
when sending a new version of the patch next time. For example:
https://lore.kernel.org/all/20250828171242.59810-1-sj@kernel.org/
Thanks
Yaxin
Powered by blists - more mailing lists