From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
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 09:54:48 +0200 [thread overview]
Message-ID: <1440402888.3430.18.camel@gmail.com> (raw)
In-Reply-To: <20150824074141.GA19209@gmail.com>
On Mon, 2015-08-24 at 09:41 +0200, Ingo Molnar wrote:
> * Mike Galbraith <umgwanakikbuti@gmail.com> wrote:
>
> > On Mon, 2015-08-24 at 08:44 +0200, Ingo Molnar wrote:
> >
> > > 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);
> >
> > There can be, and had better be if box is big, multiple housekeepers.
>
> Yes - but that does not seem to be possible via the code right now AFAICS, so at
> minimum it's incomplete.
In master housekeepers are set up in tick_nohz_init(). Everybody who's
not a nohz_full CPU is a housekeeper.
-Mike
next prev parent reply other threads:[~2015-08-24 7:54 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 [this message]
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
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=1440402888.3430.18.camel@gmail.com \
--to=umgwanakikbuti@gmail.com \
--cc=cl@linux.com \
--cc=cmetcalf@ezchip.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--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