From: Peter Zijlstra <peterz@infradead.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
vschneid@redhat.com, hannes@cmpxchg.org, surenb@google.com,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/4] sched: Define sched_clock_irqtime as static key
Date: Fri, 1 Nov 2024 11:06:17 +0100 [thread overview]
Message-ID: <20241101100617.GV14555@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20241101031750.1471-2-laoar.shao@gmail.com>
On Fri, Nov 01, 2024 at 11:17:47AM +0800, Yafang Shao wrote:
> Since CPU time accounting is a performance-critical path, let's define
> sched_clock_irqtime as a static key to minimize potential overhead.
>
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> ---
> kernel/sched/cputime.c | 16 +++++++---------
> kernel/sched/sched.h | 1 +
> 2 files changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/kernel/sched/cputime.c b/kernel/sched/cputime.c
> index 0bed0fa1acd9..d0b6ea737d04 100644
> --- a/kernel/sched/cputime.c
> +++ b/kernel/sched/cputime.c
> @@ -7,6 +7,8 @@
> #include <asm/cputime.h>
> #endif
>
> +DEFINE_STATIC_KEY_FALSE(sched_clock_irqtime);
> +
> #ifdef CONFIG_IRQ_TIME_ACCOUNTING
>
> /*
> @@ -22,16 +24,14 @@
> */
> DEFINE_PER_CPU(struct irqtime, cpu_irqtime);
>
> -static int sched_clock_irqtime;
> -
> void enable_sched_clock_irqtime(void)
> {
> - sched_clock_irqtime = 1;
> + static_branch_enable(&sched_clock_irqtime);
> }
>
> void disable_sched_clock_irqtime(void)
> {
> - sched_clock_irqtime = 0;
> + static_branch_disable(&sched_clock_irqtime);
> }
>
> static void irqtime_account_delta(struct irqtime *irqtime, u64 delta,
> @@ -57,7 +57,7 @@ void irqtime_account_irq(struct task_struct *curr, unsigned int offset)
> s64 delta;
> int cpu;
>
> - if (!sched_clock_irqtime)
> + if (!static_branch_likely(&sched_clock_irqtime))
> return;
>
> cpu = smp_processor_id();
> @@ -90,8 +90,6 @@ static u64 irqtime_tick_accounted(u64 maxtime)
>
> #else /* CONFIG_IRQ_TIME_ACCOUNTING */
>
> -#define sched_clock_irqtime (0)
> -
> static u64 irqtime_tick_accounted(u64 dummy)
> {
> return 0;
This makes no sense... in the IRQ_TIME_ACCOUNTING=n case you shouldn't
be using the static key.
> @@ -478,7 +476,7 @@ void account_process_tick(struct task_struct *p, int user_tick)
> if (vtime_accounting_enabled_this_cpu())
> return;
>
> - if (sched_clock_irqtime) {
> + if (static_branch_likely(&sched_clock_irqtime)) {
> irqtime_account_process_tick(p, user_tick, 1);
> return;
> }
> @@ -507,7 +505,7 @@ void account_idle_ticks(unsigned long ticks)
> {
> u64 cputime, steal;
>
> - if (sched_clock_irqtime) {
> + if (static_branch_likely(&sched_clock_irqtime)) {
> irqtime_account_idle_ticks(ticks);
> return;
> }
> diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> index 081519ffab46..038ce65d6635 100644
> --- a/kernel/sched/sched.h
> +++ b/kernel/sched/sched.h
> @@ -3179,6 +3179,7 @@ struct irqtime {
> };
>
> DECLARE_PER_CPU(struct irqtime, cpu_irqtime);
> +DECLARE_STATIC_KEY_FALSE(sched_clock_irqtime);
>
> /*
> * Returns the irqtime minus the softirq time computed by ksoftirqd.
> --
> 2.43.5
>
next prev parent reply other threads:[~2024-11-01 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 3:17 [PATCH v4 0/4] sched: Fix irq accounting for CONFIG_IRQ_TIME_ACCOUNTING Yafang Shao
2024-11-01 3:17 ` [PATCH v4 1/4] sched: Define sched_clock_irqtime as static key Yafang Shao
2024-11-01 10:06 ` Peter Zijlstra [this message]
2024-11-01 11:55 ` Yafang Shao
2024-11-01 3:17 ` [PATCH v4 2/4] sched: Don't account irq time if sched_clock_irqtime is disabled Yafang Shao
2024-11-01 3:17 ` [PATCH v4 3/4] sched, psi: " Yafang Shao
2024-11-01 3:17 ` [PATCH v4 4/4] sched: Fix cgroup irq accounting for CONFIG_IRQ_TIME_ACCOUNTING Yafang Shao
2024-11-01 10:28 ` Peter Zijlstra
2024-11-01 12:04 ` Yafang Shao
2024-11-01 10:54 ` [PATCH v4 0/4] sched: Fix " Peter Zijlstra
2024-11-01 11:54 ` Yafang Shao
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=20241101100617.GV14555@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bsegall@google.com \
--cc=cgroups@vger.kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=surenb@google.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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