From: Peter Zijlstra <peterz@infradead.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: paulmck@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
mingo@kernel.org, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, rostedt@goodmis.org,
dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com,
fweisbec@gmail.com, oleg@redhat.com, bobby.prani@gmail.com
Subject: Re: [PATCH tip/core/rcu 0/4] Programmatic nestable expedited grace periods
Date: Fri, 20 Feb 2015 18:43:59 +0100 [thread overview]
Message-ID: <20150220174359.GW5029@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <54E76FB7.4060005@linux.intel.com>
On Fri, Feb 20, 2015 at 09:32:39AM -0800, Arjan van de Ven wrote:
> there's a few others as well that I'm chasing down...
> .. but the flip side, prior to running ring 3 code, why NOT do fast expedites?
So my objections are twofold:
- I object to fast expedites in principle; they spray IPIs across the
system, so ideally we'd not have them at all, therefore also not at
boot.
Because as soon as the option exists, people will use it for other
things too.
- The proposed interface is very much exposed to everybody who wants
it; this again is wide open to (ab)use.
Once it exists people will start to use, and before you know it we'll
always have that fast counter incremented and we're in IPI hell. Most
likely because someone was lazy and it seemed like a quick fix for
some stupid code.
And esp. in bootup code you can special case a lot of stuff; there's
limited concurrency esp. because userspace it not there yet. So we might
not actually need those sync calls.
next prev parent reply other threads:[~2015-02-20 17:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 5:08 [PATCH tip/core/rcu 0/4] Programmatic nestable expedited grace periods Paul E. McKenney
2015-02-20 5:09 ` [PATCH v2 RFC tip/core/rcu 1/4] rcu: Provide rcu_expedite_gp() and rcu_unexpedite_gp() Paul E. McKenney
2015-02-20 5:09 ` [PATCH v2 RFC tip/core/rcu 2/4] rcu: Add rcu_expedite_gp() and rcu_unexpedite_gp() to rcutorture Paul E. McKenney
2015-02-20 5:09 ` [PATCH v2 RFC tip/core/rcu 3/4] rcu: Update from rcu_expedited variable to rcu_gp_is_expedited() Paul E. McKenney
2015-02-20 5:09 ` [PATCH v2 RFC tip/core/rcu 4/4] rcu: Add Kconfig option to expedite grace periods during boot Paul E. McKenney
2015-02-20 9:11 ` [PATCH tip/core/rcu 0/4] Programmatic nestable expedited grace periods Peter Zijlstra
2015-02-20 16:37 ` Paul E. McKenney
2015-02-20 16:54 ` Peter Zijlstra
2015-02-20 17:14 ` Paul E. McKenney
2015-02-20 17:32 ` Arjan van de Ven
2015-02-20 17:43 ` Peter Zijlstra [this message]
2015-02-20 17:45 ` Arjan van de Ven
2015-02-21 16:08 ` Peter Zijlstra
2015-02-22 1:43 ` Paul E. McKenney
2015-02-20 18:38 ` Paul E. McKenney
2015-02-21 16:11 ` Peter Zijlstra
2015-02-21 17:59 ` Paul E. McKenney
2015-02-20 18:27 ` Paul E. McKenney
2015-02-20 18:29 ` Arjan van de Ven
2015-02-20 18:39 ` Paul E. McKenney
2015-02-21 15:51 ` Arjan van de Ven
2015-02-21 18:00 ` Paul E. McKenney
2015-02-22 3:58 ` Josh Triplett
2015-02-22 6:10 ` Paul E. McKenney
2015-02-22 18:31 ` Arjan van de Ven
2015-02-22 18:48 ` Josh Triplett
2015-02-21 6:04 ` Josh Triplett
2015-02-21 15:12 ` Mathieu Desnoyers
2015-02-21 23:58 ` 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=20150220174359.GW5029@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=bobby.prani@gmail.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhart@linux.intel.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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