On 7/20/2017 10:45 PM, David Miller wrote:
From: Vijay Kumar <vijay.ac.ku...@oracle.com>
Date: Thu, 20 Jul 2017 22:36:42 -0500
I can give a try :). But looks to me one thing that will go wrong is
irq accounting done in __irq_enter() and rcu_irq_enter().
Actually, the bigger problem is that scheduler_ipi() can raise a
software interrupt, and nothing will invoke it.
Yes, I see your point.
It's turning quite ugly to avoid the IRQ overhead, I must admit.
So ignore this for now.
In the longer term a probably cleaner way to do this is to have
a special direct version of scheduler_ipi() that invokes all the
necessary work, even the rebalance softirq, directly rather than
indirectly.
Sure. Thanks.
