From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Julia Cartwright <julia@ni.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
linux-rt-users@vger.kernel.org,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: update: make RCU_EXPEDITE_BOOT default
Date: Thu, 3 Nov 2016 17:33:27 +0100 [thread overview]
Message-ID: <20161103163326.jkjbncoz7a5oriy5@linutronix.de> (raw)
In-Reply-To: <20161103162228.GG3716@linux.vnet.ibm.com>
On 2016-11-03 09:22:28 [-0700], Paul E. McKenney wrote:
> On Wed, Nov 02, 2016 at 05:30:02PM +0100, Sebastian Andrzej Siewior wrote:
> > RCU_EXPEDITE_BOOT should speed up the boot process by enforcing
> > synchronize_rcu_expedited() instead of synchronize_rcu() during the boot
> > process. There should be no reason why one does not want this and there
> > is no need worry about real time latency at this point.
> > Therefore make it default.
> >
> > Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
>
> Well, it has been awhile since I removed a Kconfig parameter.
>
> So why could this be a bad thing?
>
> 1. Very large systems might see scalability issues with unconditional
> expediting at boot. But if we don't try it, we won't know.
You mean we would make the boot process slower for them instead of
faster?
> 2. People bringing up new hardware might not want quite so many
> IPIs. But they can just set rcu_normal to prevent that.
I wanted to make things simple and not complicated…
> I am therefore queuing it for testiong and review. ;-)
Okay thanks.
> Thanx, Paul
Sebastian
next prev parent reply other threads:[~2016-11-03 16:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161012162114.GA9362@jcartwri.amer.corp.natinst.com>
[not found] ` <20161012124956.3cb5f988@redhat.com>
[not found] ` <20161012171553.GA18392@jcartwri.amer.corp.natinst.com>
[not found] ` <20161012203223.GK29518@linux.vnet.ibm.com>
[not found] ` <20161013191332-mutt-send-email-mst@kernel.org>
[not found] ` <20161014092050.GW29518@linux.vnet.ibm.com>
[not found] ` <20161016044420-mutt-send-email-mst@kernel.org>
[not found] ` <20161016112846.GR29518@linux.vnet.ibm.com>
[not found] ` <20161031173852.a3ji7hhgjis5l3u4@linutronix.de>
[not found] ` <20161031181543.GN3716@linux.vnet.ibm.com>
2016-11-02 16:30 ` [PATCH] rcu: update: make RCU_EXPEDITE_BOOT default Sebastian Andrzej Siewior
2016-11-03 16:22 ` Paul E. McKenney
2016-11-03 16:33 ` Sebastian Andrzej Siewior [this message]
2016-11-03 16:59 ` Paul E. McKenney
2016-11-07 17:19 ` Steven Rostedt
2016-11-07 17:30 ` Sebastian Andrzej Siewior
2016-11-07 17:35 ` Josh Triplett
2016-11-07 18:05 ` Paul E. McKenney
2016-11-07 18:08 ` Josh Triplett
2016-11-07 19:04 ` 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=20161103163326.jkjbncoz7a5oriy5@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=julia@ni.com \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mst@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.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).