From: Chris Metcalf <cmetcalf@ezchip.com>
To: Mike Galbraith <umgwanakikbuti@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Cc: "Jiang, Yunhong" <yunhong.jiang@intel.com>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Vatika Harlalka <vatikaharlalka@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Preeti U Murthy <preeti@linux.vnet.ibm.com>,
Christoph Lameter <cl@linux.com>,
"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/2] nohz: Affine unpinned timers to housekeepers
Date: Wed, 2 Sep 2015 12:16:30 -0400 [thread overview]
Message-ID: <55E720DE.8020100@ezchip.com> (raw)
In-Reply-To: <1441186689.4163.11.camel@gmail.com>
On 09/02/2015 05:38 AM, Mike Galbraith wrote:
> IMHO, nohz_full -> cpu_isolated_map removal really wants to happen.
> NO_HZ_FULL_ALL currently means "Woohoo, next stop NR_CPUS=0".
Yeah, the problem seems to be folks who use it as a kind of
"hey, maybe this gives me some optimization boost somewhere"
kind of setting. Did we ever hear actual use cases for people who
benefited from running nohz_full on cpus with an active scheduler,
i.e. no isolcpus for that core? I find it hard to imagine, but, maybe...?
If we don't have such use cases, what should we do here? I'm
slightly sympathetic to these folks who are going "Gee, my machine
suddenly got way slower", but only in the same sense as people
who shoot themselves in the foot and then say "Gee, my foot is
bleeding". But maybe I'm being too hard core :-)
--
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com
next prev parent reply other threads:[~2015-09-02 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 14:50 [GIT PULL] sched/nohz: Affine unpinned timers to housekeepers Frederic Weisbecker
2015-09-01 14:50 ` [PATCH 1/2] nohz: " Frederic Weisbecker
2015-09-01 19:14 ` Jiang, Yunhong
2015-09-01 20:47 ` Frederic Weisbecker
2015-09-02 9:38 ` Mike Galbraith
2015-09-02 12:33 ` Mike Galbraith
2015-09-02 16:16 ` Chris Metcalf [this message]
2015-09-02 19:03 ` Jiang, Yunhong
2015-09-03 1:29 ` Mike Galbraith
2015-09-04 15:56 ` Luiz Capitulino
2015-09-04 17:19 ` Frederic Weisbecker
2015-09-02 15:57 ` [tip:sched/urgent] " tip-bot for Vatika Harlalka
2015-09-01 14:51 ` [PATCH 2/2] nohz: Assert existing housekeepers when nohz full enabled Frederic Weisbecker
2015-09-02 15:57 ` [tip:sched/urgent] " tip-bot for 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=55E720DE.8020100@ezchip.com \
--to=cmetcalf@ezchip.com \
--cc=cl@linux.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=umgwanakikbuti@gmail.com \
--cc=vatikaharlalka@gmail.com \
--cc=yunhong.jiang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.