From: Steven Rostedt <rostedt@goodmis.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Uladzislau Rezki <urezki@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
Alison Chaiken <achaiken@aurora.tech>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>, RCU <rcu@vger.kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <neeraj.iitr10@gmail.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: Re: [PATCH] rcu/nocb: Add an option to ON/OFF an offloading from RT context
Date: Tue, 10 May 2022 10:09:46 -0400 [thread overview]
Message-ID: <20220510100946.5fdff700@gandalf.local.home> (raw)
In-Reply-To: <20220509183934.GQ1790663@paulmck-ThinkPad-P17-Gen-1>
On Mon, 9 May 2022 11:39:34 -0700
"Paul E. McKenney" <paulmck@kernel.org> wrote:
> This allows your current RCU_NOCB_CPU_CB_BOOST with something like
> this in place of the "default n":
>
> default y if PREEMPT_RT
> default n if !PREEMPT_RT
BTW, I don't think you need the !PREEMPT_RT, because all configs are
'n' by default. That is:
default y if PREEMPT_RT
should be good enough.
-- Steve
next prev parent reply other threads:[~2022-05-10 14:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 10:16 [PATCH] rcu/nocb: Add an option to ON/OFF an offloading from RT context Uladzislau Rezki (Sony)
2022-05-05 19:09 ` Paul E. McKenney
2022-05-06 16:22 ` Uladzislau Rezki
2022-05-06 18:24 ` Paul E. McKenney
2022-05-07 9:11 ` Uladzislau Rezki
2022-05-07 22:32 ` Paul E. McKenney
2022-05-08 6:28 ` Joel Fernandes
2022-05-08 21:32 ` Paul E. McKenney
2022-05-09 0:17 ` Joel Fernandes
2022-05-09 3:37 ` Paul E. McKenney
2022-05-09 17:17 ` Joel Fernandes
2022-05-09 18:14 ` Paul E. McKenney
2022-05-09 18:28 ` Uladzislau Rezki
2022-05-09 18:39 ` Paul E. McKenney
2022-05-09 18:43 ` Uladzislau Rezki
2022-05-10 14:09 ` Steven Rostedt [this message]
2022-05-10 14:24 ` Paul E. McKenney
2022-05-10 14:35 ` Uladzislau Rezki
2022-05-10 14:01 ` Steven Rostedt
2022-05-11 13:39 ` Uladzislau Rezki
2022-05-11 14:29 ` Steven Rostedt
2022-05-11 14:51 ` Uladzislau Rezki
2022-05-11 14:53 ` Uladzislau Rezki
2022-05-11 17:17 ` Uladzislau Rezki
2022-05-16 16:22 ` Steven Rostedt
2022-05-16 16:42 ` Uladzislau Rezki
2022-05-10 14:07 ` Sebastian Andrzej Siewior
2022-05-10 17:14 ` 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=20220510100946.5fdff700@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=achaiken@aurora.tech \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.iitr10@gmail.com \
--cc=oleksiy.avramchenko@sony.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=urezki@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