From: Frederic Weisbecker <frederic@kernel.org>
To: Zhen Lei <thunder.leizhen@huawei.com>
Cc: "Paul E . McKenney" <paulmck@kernel.org>,
Neeraj Upadhyay <quic_neeraju@quicinc.com>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
Robert Elliott <elliott@hpe.com>
Subject: Re: [PATCH v7 2/6] sched: Add helper kstat_cpu_softirqs_sum()
Date: Mon, 14 Nov 2022 12:42:52 +0100 [thread overview]
Message-ID: <20221114114252.GA590078@lothringen> (raw)
In-Reply-To: <20221111130709.247-3-thunder.leizhen@huawei.com>
On Fri, Nov 11, 2022 at 09:07:05PM +0800, Zhen Lei wrote:
> Similar to kstat_cpu_irqs_sum(), it counts the sum of all software
> interrupts on a specified CPU.
>
> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
> ---
> include/linux/kernel_stat.h | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/include/linux/kernel_stat.h b/include/linux/kernel_stat.h
> index 90e2fdc17d79ff8..898076e173a928a 100644
> --- a/include/linux/kernel_stat.h
> +++ b/include/linux/kernel_stat.h
> @@ -67,6 +67,17 @@ static inline unsigned int kstat_softirqs_cpu(unsigned int irq, int cpu)
> return kstat_cpu(cpu).softirqs[irq];
> }
>
> +static inline unsigned int kstat_cpu_softirqs_sum(int cpu)
> +{
> + int i;
> + unsigned int sum = 0;
> +
> + for (i = 0; i < NR_SOFTIRQS; i++)
> + sum += kstat_softirqs_cpu(i, cpu);
This should return a u64 or at least an unsigned long so that high
numbers of CPUs don't overflow easily.
Thanks.
> +
> + return sum;
> +}
> +
> /*
> * Number of interrupts per specific IRQ source, since bootup
> */
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-11-14 11:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 13:07 [PATCH v7 0/6] rcu: Add RCU stall diagnosis information Zhen Lei
2022-11-11 13:07 ` [PATCH v7 1/6] genirq: Fix the return type of kstat_cpu_irqs_sum() Zhen Lei
2022-11-11 13:07 ` [PATCH v7 2/6] sched: Add helper kstat_cpu_softirqs_sum() Zhen Lei
2022-11-14 11:42 ` Frederic Weisbecker [this message]
2022-11-14 12:45 ` Leizhen (ThunderTown)
2022-11-14 12:50 ` Frederic Weisbecker
2022-11-14 14:26 ` Leizhen (ThunderTown)
2022-11-11 13:07 ` [PATCH v7 3/6] sched: Add helper nr_context_switches_cpu() Zhen Lei
2022-11-11 13:07 ` [PATCH v7 4/6] rcu: Add RCU stall diagnosis information Zhen Lei
2022-11-14 11:24 ` Frederic Weisbecker
2022-11-14 12:32 ` Leizhen (ThunderTown)
2022-11-14 12:46 ` Frederic Weisbecker
2022-11-16 22:39 ` Frederic Weisbecker
2022-11-17 1:57 ` Leizhen (ThunderTown)
2022-11-17 12:22 ` Frederic Weisbecker
2022-11-17 13:25 ` Leizhen (ThunderTown)
2022-11-17 14:26 ` Frederic Weisbecker
2022-11-18 2:03 ` Leizhen (ThunderTown)
2022-11-11 13:07 ` [PATCH v7 5/6] doc: Document CONFIG_RCU_CPU_STALL_CPUTIME=y stall information Zhen Lei
2022-11-16 22:55 ` Frederic Weisbecker
2022-11-17 2:03 ` Leizhen (ThunderTown)
2022-11-17 12:23 ` Frederic Weisbecker
2022-11-11 13:07 ` [PATCH v7 6/6] rcu: Align the output of RCU stall Zhen Lei
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=20221114114252.GA590078@lothringen \
--to=frederic@kernel.org \
--cc=elliott@hpe.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=thunder.leizhen@huawei.com \
/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