On 7/20/2017 10:45 PM, David Miller wrote:
From: Vijay Kumar
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
s
From: Vijay Kumar
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
On 7/20/2017 9:55 PM, David Miller wrote:
From: Vijay Kumar
Date: Thu, 20 Jul 2017 21:44:24 -0500
I had same thoughts initially but I had to go with this approach as
scheduler_ipi is wrapped with irq_enter() and irq_exit(). Whereas POKE
resumes the cpu in process context.
Comments in schedu
From: Vijay Kumar
Date: Thu, 20 Jul 2017 21:44:24 -0500
> I had same thoughts initially but I had to go with this approach as
> scheduler_ipi is wrapped with irq_enter() and irq_exit(). Whereas POKE
> resumes the cpu in process context.
>
> Comments in scheduler_ipi():
>
> * Not all re
On 7/20/2017 2:57 PM, David Miller wrote:
From: Vijay Kumar
Date: Sat, 8 Jul 2017 14:23:42 -0600
cpu_poke is a low latency path to resume the target cpu if suspended
using cpu_yield. Use cpu poke to resume cpu if supported by hypervisor.
hackbench results (lower is better):
Nu
From: Vijay Kumar
Date: Sat, 8 Jul 2017 14:23:42 -0600
> cpu_poke is a low latency path to resume the target cpu if suspended
> using cpu_yield. Use cpu poke to resume cpu if supported by hypervisor.
>
>hackbench results (lower is better):
> Number of
> Process:
cpu_poke is a low latency path to resume the target cpu if suspended
using cpu_yield. Use cpu poke to resume cpu if supported by hypervisor.
hackbench results (lower is better):
Number of
Process:w/o fix with fix
1 0.012
7 matches
Mail list logo
