From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Vatika Harlalka <vatikaharlalka@gmail.com>,
Chris Metcalf <cmetcalf@ezchip.com>,
Thomas Gleixner <tglx@linutronix.de>,
Preeti U Murthy <preeti@linux.vnet.ibm.com>,
Christoph Lameter <cl@linux.com>
Subject: Re: [PATCH RESEND] sched/nohz: Affine unpinned timers to housekeepers
Date: Mon, 24 Aug 2015 06:50:18 -0700 [thread overview]
Message-ID: <20150824135018.GE11078@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150824064412.GA11581@gmail.com>
On Mon, Aug 24, 2015 at 08:44:12AM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:
>
> > > here it's fully set - triggering the bug I'm worried about. So what am I
> > > missing, what prevents CONFIG_NO_HZ_FULL_ALL from crashing?
> >
> > The boot CPU is excluded from tick_nohz_full_mask in tick_nohz_init(), which is
> > called from tick_init() which is called from start_kernel() shortly after
> > rcu_init():
> >
> > cpu = smp_processor_id();
> >
> > if (cpumask_test_cpu(cpu, tick_nohz_full_mask)) {
> > pr_warning("NO_HZ: Clearing %d from nohz_full range for timekeeping\n", cpu);
> > cpumask_clear_cpu(cpu, tick_nohz_full_mask);
> > }
> >
> > This happens after the call to tick_nohz_init_all() that does the
> > cpumask_setall() that you called out above.
>
> Ah, indeed - I somehow missed that.
>
> This brings up two other questions:
>
> 1)
>
> the 'housekeeping CPU' is essentially the boot CPU. Yet we dedicate a full mask to
> it (housekeeping_mask - a variable mask to begin with) and recover the
> housekeeping CPU via:
>
> + return cpumask_any_and(housekeeping_mask, cpu_online_mask);
>
> which can be pretty expensive, and which gets executed in two hotpaths:
>
> kernel/time/hrtimer.c: return &per_cpu(hrtimer_bases, get_nohz_timer_target());
> kernel/time/timer.c: return per_cpu_ptr(&tvec_bases, get_nohz_timer_target());
>
> ... why not just use a single housekeeping_cpu which would be way faster to pass
> down to the timer code?
The housekeeping_cpu came later, but that does seem like a good optimization.
> 2)
>
> What happens if the boot CPU is offlined? (under CONFIG_BOOTPARAM_HOTPLUG_CPU0=y)
>
> I don't see CPU hotplug callbacks fixing up the housekeeping_mask if the boot CPU
> is offlined.
The tick_nohz_cpu_down_callback() function does this, though in a less
than obvious way. The tick_do_timer_cpu variable is the housekeeping
CPU that is currently handling timing, and it is not permitted to go
offline.
Thanx, Paul
next prev parent reply other threads:[~2015-08-24 13:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 1:46 [PATCH RESEND] sched/nohz: Affine unpinned timers to housekeepers Frederic Weisbecker
2015-08-22 21:09 ` Ping: " Frederic Weisbecker
2015-08-23 1:22 ` Christoph Lameter
2015-08-23 5:40 ` Ingo Molnar
2015-08-23 16:01 ` Paul E. McKenney
2015-08-24 1:28 ` Frederic Weisbecker
2015-08-24 6:44 ` Ingo Molnar
2015-08-24 7:23 ` Mike Galbraith
2015-08-24 7:41 ` Ingo Molnar
2015-08-24 7:54 ` Mike Galbraith
2015-08-24 8:00 ` Ingo Molnar
2015-08-24 13:36 ` Frederic Weisbecker
2015-08-24 14:01 ` Mike Galbraith
2015-08-25 8:29 ` Ingo Molnar
2015-08-25 13:45 ` Frederic Weisbecker
2015-08-28 8:32 ` Ingo Molnar
2015-08-28 12:30 ` Frederic Weisbecker
2015-08-24 13:50 ` Paul E. McKenney [this message]
2015-08-24 14:04 ` Frederic Weisbecker
2015-08-24 15:45 ` Paul E. McKenney
2015-08-24 1:45 ` Frederic Weisbecker
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=20150824135018.GE11078@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=cl@linux.com \
--cc=cmetcalf@ezchip.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=vatikaharlalka@gmail.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