From: "Paul E. McKenney" <paulmck@kernel.org>
To: "Elliott, Robert (Servers)" <elliott@hpe.com>
Cc: Zhen Lei <thunder.leizhen@huawei.com>,
Frederic Weisbecker <frederic@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" <rcu@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] sched: Add helper kstat_cpu_softirqs_sum()
Date: Fri, 28 Oct 2022 10:57:09 -0700 [thread overview]
Message-ID: <20221028175709.GP5600@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <MW5PR84MB18423C3F30D3F789EB48D0A5AB339@MW5PR84MB1842.NAMPRD84.PROD.OUTLOOK.COM>
On Thu, Oct 27, 2022 at 07:04:53PM +0000, Elliott, Robert (Servers) wrote:
>
> > Similar to kstat_cpu_irqs_sum(), it counts the sum of all software
> > interrupts on a specified CPU.
> >
> > diff --git 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);
> > +
> > + return sum;
> > +}
>
> In the function upon which this is based:
>
> irqs_sumstruct kernel_stat {
> unsigned long irqs_sum;
> unsigned int softirqs[NR_SOFTIRQS];
> };
>
> static inline unsigned int kstat_cpu_irqs_sum(unsigned int cpu)
> {
> return kstat_cpu(cpu).irqs_sum;
> }
>
> kstat_cpu_irqs_sum returns an unsigned long as an unsigned int, which
> could cause large values to be truncated. Should that return
> unsigned long? The only existing caller is fs/proc/stat.c which
> puts it into a u64:
> u64 sum = 0;
> ...
> sum += kstat_cpu_irqs_sum(i);
>
> The softirqs field is an unsigned int, so the new function doesn't have
> this inconsistency.
Good point!
Zhen Lei, thoughts?
Thanx, Paul
next prev parent reply other threads:[~2022-10-28 17:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-22 12:45 [PATCH v2 0/3] rcu: Add RCU stall diagnosis information Zhen Lei
2022-10-22 12:45 ` [PATCH v2 1/3] sched: Add helper kstat_cpu_softirqs_sum() Zhen Lei
2022-10-27 19:04 ` Elliott, Robert (Servers)
2022-10-28 2:38 ` Leizhen (ThunderTown)
2022-10-28 22:35 ` Paul E. McKenney
2022-10-29 9:51 ` Leizhen (ThunderTown)
2022-10-28 17:57 ` Paul E. McKenney [this message]
2022-10-22 12:45 ` [PATCH v2 2/3] sched: Add helper nr_context_switches_cpu() Zhen Lei
2022-10-22 12:45 ` [PATCH v2 3/3] rcu: Add RCU stall diagnosis information Zhen Lei
2022-10-27 17:33 ` Paul E. McKenney
2022-10-28 3:16 ` Leizhen (ThunderTown)
2022-10-28 22:55 ` Paul E. McKenney
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=20221028175709.GP5600@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=elliott@hpe.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--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
all inboxes | Powered by JetHome®