mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [PATCH] sched/isolation: reconcile rcu_nocbs= and nohz_full=
Date: Fri, 14 May 2021 08:55:22 +0200	[thread overview]
Message-ID: <YJ4e2j+FewuJ4zdZ@gmail.com> (raw)
In-Reply-To: <20210513142216.GZ975577@paulmck-ThinkPad-P17-Gen-1>


* Paul E. McKenney <paulmck@kernel.org> wrote:

> On Thu, May 13, 2021 at 02:13:28PM +0200, Ingo Molnar wrote:
> > 
> > * Paul E. McKenney <paulmck@kernel.org> wrote:
> > 
> > > On Mon, Apr 19, 2021 at 12:26:59AM -0400, Paul Gortmaker wrote:
> > > > We have a mismatch between RCU and isolation -- in relation to what is
> > > > considered the maximum valid CPU number.
> > > > 
> > > > This matters because nohz_full= and rcu_nocbs= are joined at the hip; in
> > > > fact the former will enforce the latter.  So we don't want a CPU mask to
> > > > be valid for one and denied for the other.
> > > > 
> > > > The difference 1st appeared as of v4.15; further details are below.
> > > 
> > > I pulled this into -rcu for testing and further review.
> > > 
> > > If it should instead go through some other tree:
> > > 
> > > Acked-by: Paul E. McKenney <paulmck@kernel.org>
> > 
> > Thanks - added this fix to tip:sched/core.
> 
> Very good, I will drop it from -rcu later today, Pacific Time.

Thank you!

	Ingo

  reply	other threads:[~2021-05-14  6:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19  4:26 Paul Gortmaker
2021-04-22 21:24 ` Paul E. McKenney
2021-05-13 12:13   ` Ingo Molnar
2021-05-13 14:22     ` Paul E. McKenney
2021-05-14  6:55       ` Ingo Molnar [this message]
2021-05-13 13:17 ` [tip: sched/core] sched/isolation: Reconcile " tip-bot2 for Paul Gortmaker

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=YJ4e2j+FewuJ4zdZ@gmail.com \
    --to=mingo@kernel.org \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®