stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Josh Triplett <josh@joshtriplett.org>,
	rostedt <rostedt@goodmis.org>,
	Lai Jiangshan <jiangshanlai@gmail.com>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH] Fix: disable sys_membarrier when nohz_full is enabled
Date: Sat, 12 Nov 2016 09:58:20 -0800	[thread overview]
Message-ID: <20161112175820.GV4127@linux.vnet.ibm.com> (raw)
In-Reply-To: <26153082.18614.1478603751607.JavaMail.zimbra@efficios.com>

On Tue, Nov 08, 2016 at 11:15:51AM +0000, Mathieu Desnoyers wrote:
> ----- On Nov 7, 2016, at 3:03 PM, Paul E. McKenney paulmck@linux.vnet.ibm.com wrote:
> 
> > On Mon, Nov 07, 2016 at 06:10:14PM +0000, Mathieu Desnoyers wrote:
> >> 
> >> ----- On Nov 7, 2016, at 1:06 PM, Paul E. McKenney paulmck@linux.vnet.ibm.com
> >> wrote:
> >> 
> >> > On Mon, Nov 07, 2016 at 05:08:59PM +0000, Mathieu Desnoyers wrote:
> >> >> ----- On Nov 3, 2016, at 1:49 PM, Paul E. McKenney paulmck@linux.vnet.ibm.com
> >> >> wrote:
> >> >> 
> >> >> > On Thu, Nov 03, 2016 at 10:29:28AM -0600, Mathieu Desnoyers wrote:
> >> >> >> Userspace applications should be allowed to expect the membarrier system
> >> >> >> call with MEMBARRIER_CMD_SHARED command to issue memory barriers on
> >> >> >> nohz_full CPUs, but synchronize_sched() does not take those into
> >> >> >> account.
> >> >> >> 
> >> >> >> Given that we do not want unrelated processes to be able to affect
> >> >> >> real-time sensitive nohz_full CPUs, simply return ENOSYS when membarrier
> >> >> >> is invoked on a kernel with enabled nohz_full CPUs.
> >> >> >> 
> >> >> >> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> >> >> >> CC: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> >> >> > 
> >> >> > Acked-by: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> >> >> 
> >> >> Hi Paul,
> >> >> 
> >> >> Do you plan to pick it up through your tree, or I should sent
> >> >> it directly to Linus ?
> >> > 
> >> > Your choice.  I believe that the original went some other way, but I
> >> > would be fine carrying this one.
> >> 
> >> Not sure what you mean by "the original" ? And which other way ?
> >> I have not been notified about this.
> > 
> > If I remember correctly, you sent the original sys_membarrier()
> > patch through akpm or similar.
> 
> Ah right, the original implementation, yes.
> 
> > 
> >> If you can carry this patch it would be very much appreciated,
> > 
> > Will do!
> 
> Especially since the regression is somewhat related to RCU
> behavior wrt nohz_full, getting it through your tree seems
> relevant.

I have it queued for 4.11, thank you!

							Thanx, Paul


  reply	other threads:[~2016-11-12 17:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 16:29 [PATCH] Fix: disable sys_membarrier when nohz_full is enabled Mathieu Desnoyers
2016-11-03 17:49 ` Paul E. McKenney
2016-11-07 17:08   ` Mathieu Desnoyers
2016-11-07 18:06     ` Paul E. McKenney
2016-11-07 18:10       ` Mathieu Desnoyers
2016-11-07 20:03         ` Paul E. McKenney
2016-11-08 11:15           ` Mathieu Desnoyers
2016-11-12 17:58             ` Paul E. McKenney [this message]
2016-11-17  6:51 ` Lai Jiangshan
2016-11-17 11:46   ` Mathieu Desnoyers
2016-11-17 13:40     ` Paul E. McKenney
2016-11-17 13:54       ` Mathieu Desnoyers
2016-11-17 14:09         ` Paul E. McKenney
2016-11-17 14:50         ` Steven Rostedt
2016-11-17 15:02           ` Mathieu Desnoyers
2016-11-17 15:17             ` Steven Rostedt
2016-11-17 16:02               ` Paul E. McKenney
2016-11-17 13:38   ` Paul E. McKenney

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=20161112175820.GV4127@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=rostedt@goodmis.org \
    --cc=stable@vger.kernel.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).