Re: [PATCH 05/10] smp: Fast path check on IPI list

2014-07-29 Thread Frederic Weisbecker
On Tue, Jul 29, 2014 at 02:07:39PM +0200, Peter Zijlstra wrote: > On Mon, Jul 28, 2014 at 07:37:31PM +0200, Frederic Weisbecker wrote: > > When we enqueue a remote irq work, we trigger the same IPI as those > > raised by smp_call_function_*() family. > > > > So when we receive such IPI, we check b

Re: [PATCH 05/10] smp: Fast path check on IPI list

2014-07-29 Thread Frederic Weisbecker
On Tue, Jul 29, 2014 at 02:07:39PM +0200, Peter Zijlstra wrote: > On Mon, Jul 28, 2014 at 07:37:31PM +0200, Frederic Weisbecker wrote: > > When we enqueue a remote irq work, we trigger the same IPI as those > > raised by smp_call_function_*() family. > > > > So when we receive such IPI, we check b

Re: [PATCH 05/10] smp: Fast path check on IPI list

2014-07-29 Thread Peter Zijlstra
On Mon, Jul 28, 2014 at 07:37:31PM +0200, Frederic Weisbecker wrote: > When we enqueue a remote irq work, we trigger the same IPI as those > raised by smp_call_function_*() family. > > So when we receive such IPI, we check both irq_work and smp_call_function > queues. Thus if we trigger a remote i

[PATCH 05/10] smp: Fast path check on IPI list

2014-07-28 Thread Frederic Weisbecker
When we enqueue a remote irq work, we trigger the same IPI as those raised by smp_call_function_*() family. So when we receive such IPI, we check both irq_work and smp_call_function queues. Thus if we trigger a remote irq work, we'll likely find the smp_call_function queue empty unless we collide

[PATCH 05/10] smp: Fast path check on IPI list

2014-07-18 Thread Frederic Weisbecker
When we enqueue a remote irq work, we trigger the same IPI as those raised by smp_call_function_*() family. So when we receive such IPI, we check both irq_work and smp_call_function queues. Thus if we trigger a remote irq work, we'll likely find the smp_call_function queue empty unless we collide