Re: [PATCH RFC tip/core/rcu] Parallelize and economize NOCB kthread wakeups

[Frederic Weisbecker <fweisbec@gmail.com>]

On Thu, Jul 03, 2014 at 07:48:40AM +0200, Mike Galbraith wrote:
> On Wed, 2014-07-02 at 22:21 -0700, Paul E. McKenney wrote: 
> > On Thu, Jul 03, 2014 at 05:31:19AM +0200, Mike Galbraith wrote:
> 
> > > NO_HZ_FULL is a property of a set of CPUs.  isolcpus is supposed to go
> > > away as being a redundant interface to manage a single property of a set
> > > of CPUs, but it's perfectly fine for NO_HZ_FULL to add an interface to
> > > manage a single property of a set of CPUs.  What am I missing? 
> > 
> > Well, for now, it can only be specified at build time or at boot time.
> > In theory, it is possible to change a CPU from being callback-offloaded
> > to not at runtime, but there would need to be an extremely good reason
> > for adding that level of complexity.  Lots of "fun" races in there...
> 
> Yeah, understood.
> 
> (still it's a NO_HZ_FULL wart though IMHO, would be prettier and more
> usable if it eventually became unified with cpuset and learned how to
> tap-dance properly;)

Well, the exact same goes for NO_HZ_FULL, quoting Paul (just replacing RCU things
with dynticks) it becomes:

 "it can only be specified at build time or at boot time.
  In theory, it is possible to change a CPU from being idle-dynticks
  to full-dynticks at runtime, but there would need to be an extremely good reason
  for adding that level of complexity.  Lots of "fun" races in there..."

And I'm not even sure that somebody actually uses full dynticks today. I only know
that some financial institutions are considering it, which is not cheering me up
much...

So we are very far from that day when we'll migrate to a runtime interface.