From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Josh Triplett <josh@joshtriplett.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
rostedt <rostedt@goodmis.org>,
Nicholas Miell <nmiell@comcast.net>,
Ingo Molnar <mingo@redhat.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
David Howells <dhowells@redhat.com>,
bobby prani <bobby.prani@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Shuah Khan <shuahkh@osg.samsung.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH] membarrier: handle nohz_full with expedited thread registration
Date: Tue, 17 Jan 2017 12:53:21 -0800 [thread overview]
Message-ID: <20170117205321.GF5238@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170117035521.GB2787@lerouge>
On Tue, Jan 17, 2017 at 04:55:22AM +0100, Frederic Weisbecker wrote:
[ . . . ]
> In fact due to the complexity involved, I have to ask first if we
> really need this feature. Typically nohz_full workloads don't want to
> be disturbed at all, so do we have real and significant usecases of CPU
> isolation workloads that want to be concerned by this membarrier so much
> that they can tolerate some random IRQ?
I believe that we need to explore the options for implementing it and
to -at- -least- have a patch ready, even if that patch doesn't go
upstream immediately.
Thanx, Paul
next prev parent reply other threads:[~2017-01-17 22:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 19:51 [RFC PATCH] membarrier: handle nohz_full with expedited thread registration Mathieu Desnoyers
2017-01-16 20:15 ` Linus Torvalds
2017-01-16 22:56 ` Mathieu Desnoyers
2017-01-16 23:50 ` Linus Torvalds
2017-01-17 2:09 ` Mathieu Desnoyers
2017-01-17 3:55 ` Frederic Weisbecker
2017-01-17 20:53 ` Paul E. McKenney [this message]
2017-01-18 11:00 ` Peter Zijlstra
2017-01-19 22:01 ` Paul McKenney
2017-01-17 21:56 ` Mathieu Desnoyers
2017-01-17 23:29 ` Steven Rostedt
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=20170117205321.GF5238@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=fweisbec@gmail.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=josh@joshtriplett.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=nmiell@comcast.net \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shuahkh@osg.samsung.com \
--cc=stephen@networkplumber.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).