nohz: Move nohz kick out of scheduler IPI, v5
Subsystems (2)
cover nohz: Move nohz kick out of scheduler IPI, v5
So I removed all the part that tried to avoid the tick for the nohz IPI since the lockdep report I saw was actually about other issues related to locking scenarios of my own brain.
Now it's much simplified!
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
timers/nohz-irq-work-v3
Thanks,
Frederic
---
Frederic Weisbecker (3):
irq_work: Implement remote queueing
nohz: Move full nohz kick to its own IPI
nohz: Use IPI implicit full barrier against rq->nr_running r/w
include/linux/irq_work.h | 2 ++ include/linux/tick.h | 9 ++++++++- kernel/irq_work.c | 19 ++++++++++++++++++- kernel/sched/core.c | 14 ++++++-------- kernel/sched/sched.h | 12 +++++++++--- kernel/smp.c | 4 ++++ kernel/time/tick-sched.c | 10 ++++++---- 7 files changed, 53 insertions(+), 17 deletions(-)
PATCH 1/3 irq_work: Implement remote queueing
irq work currently only supports local callbacks. However its code is mostly ready to run remote callbacks and we have some potential user.
The full nohz subsystem currently open codes its own remote irq work on top of the scheduler ipi when it wants a CPU to reevaluate its next tick. However this ad hoc solution bloats the scheduler IPI.
Lets just extend the irq work subsystem to support remote queuing on top of the generic SMP IPI to handle this kind of user. This shouldn't add noticeable overhead.
--- include/linux/irq_work.h | 2 ++ kernel/irq_work.c | 19 ++++++++++++++++++- kernel/smp.c | 4 ++++ 3 files changed, 24 insertions(+), 1 deletion(-)
include/linux/irq_work.h +2 -0
@@ -33,6 +33,8 @@ void init_irq_work(struct irq_work *work, void (*func)(struct irq_work *))#define DEFINE_IRQ_WORK (name, _f) struct irq_work name = { .func = (_f), }bool irq_work_queue (struct irq_work *work); +bool irq_work_queue_on (struct irq_work *work,int cpu); +void irq_work_run (void );void irq_work_sync (struct irq_work *work);
kernel/irq_work.c +18 -1
@@ -56,11 +56,28 @@ void __weak arch_irq_work_raise(void) }/* -* Enqueue the irq_work @entry unless it's already pending +* Enqueue the irq_work @work on @cpu unless it's already pending * somewhere. * * Can be re-enqueued while the callback is still in progress. */ +bool irq_work_queue_on (struct irq_work *work,int cpu) +{ +/* Only queue if not already pending */ +if (!irq_work_claim (work)) +return false; + +/* All work should have been flushed before going offline */ +WARN_ON_ONCE (cpu_is_offline (cpu)); + +llist_add (&work->llnode, &per_cpu (irq_work_list, cpu)); +native_send_call_func_single_ipi (cpu); + +return true; +} +EXPORT_SYMBOL_GPL (irq_work_queue_on); + +/* Enqueue the irq work @work on the current CPU */ bool irq_work_queue (struct irq_work *work) {/* Only queue if not already pending */
kernel/smp.c +4 -0
@@ -3,6 +3,7 @@* * (C) Jens Axboe <[email protected]> 2008 */ +#include <linux/irq_work.h> #include <linux/rcupdate.h> #include <linux/rculist.h> #include <linux/kernel.h>
@@ -198,6 +199,9 @@ void generic_smp_call_function_single_interrupt(void) csd->func (csd->info);csd_unlock (csd); } + +/* Handle irq works queued remotely by irq_work_queue_on() */ +irq_work_run (); }/*
Signature · 1 line
1.8.3.1
Peter Zijlstra
maintainerRe: [PATCH 1/3] irq_work: Implement remote queueing
Quoted 51 lines · Frederic Weisbecker
irq work currently only supports local callbacks. However its code is mostly ready to run remote callbacks and we have some potential user.
The full nohz subsystem currently open codes its own remote irq work on top of the scheduler ipi when it wants a CPU to reevaluate its next tick. However this ad hoc solution bloats the scheduler IPI.
Lets just extend the irq work subsystem to support remote queuing on top of the generic SMP IPI to handle this kind of user. This shouldn't add noticeable overhead.
Suggested-by Peter Zijlstra <[email protected]>Cc Andrew Morton <[email protected]>Cc Ingo Molnar <[email protected]>Cc Kevin Hilman <[email protected]>Cc Paul E. McKenney <[email protected]>Cc Peter Zijlstra <[email protected]>Cc Thomas Gleixner <[email protected]>Cc Viresh Kumar <[email protected]>Signed-off-by Frederic Weisbecker <[email protected]>--- include/linux/irq_work.h | 2 ++ kernel/irq_work.c | 19 ++++++++++++++++++- kernel/smp.c | 4 ++++ 3 files changed, 24 insertions(+), 1 deletion(-)include/linux/irq_work.h +2
-0@@ -33,6 +33,8 @@ void init_irq_work(struct irq_work *work, void (*func)(struct irq_work *))#define DEFINE_IRQ_WORK (name, _f) struct irq_work name = { .func = (_f), }bool irq_work_queue (struct irq_work *work); +bool irq_work_queue_on (struct irq_work *work,int cpu); +void irq_work_run (void );void irq_work_sync (struct irq_work *work);kernel/irq_work.c +1
-1@@ -56,11 +56,28 @@ void __weak arch_irq_work_raise(void) }/* -* Enqueue the irq_work @entry unless it's already pending +* Enqueue the irq_work @work on @cpu unless it's already pending * somewhere. *
kernel/irq_work.c void __weak arch_irq_work_raise(void) · line 71
Quoted 10 lines
kernel/irq_work.c +8
-0* Can be re-enqueued while the callback is still in progress. */ +bool irq_work_queue_on (struct irq_work *work,int cpu) +{ +/* Only queue if not already pending */ +if (!irq_work_claim (work)) +return false; + +/* All work should have been flushed before going offline */ +WARN_ON_ONCE (cpu_is_offline (cpu));
WARN_ON_ONCE(in_nmi());
kernel/irq_work.c void __weak arch_irq_work_raise(void) · line 74
Quoted 3 lines
kernel/irq_work.c +3
-0+ +llist_add (&work->llnode, &per_cpu (irq_work_list, cpu)); +native_send_call_func_single_ipi (cpu);
At the very leastestest make that:
if (llist_add(&work->llnode, &per_cpu(irq_work_list, cpu))) native_send_call_func_single_ipi(cpu);
But ideally, also test the IRQ_WORK_LAZY support, its weird to have that only be supported for the other queue.
Hmm, why do we need that LAZY crap, that completely wrecks a perfectly simple thing.
The changelog (bc6679aef673f), not the printk() usage make much sense, printk() can't cause an IPI storm... printk() isn't fast enough to storm anything.
Quoted 4 lines
kernel/irq_work.c +4
-0+ +return true; +} +EXPORT_SYMBOL_GPL (irq_work_queue_on);
Peter Zijlstra
maintainerRe: [PATCH 1/3] irq_work: Implement remote queueing
Quoted 8 lines · Peter Zijlstra
kernel/irq_work.c void __weak arch_irq_work_raise(void) · line 74
Quoted 2 lines
kernel/irq_work.c +2
-0+llist_add (&work->llnode, &per_cpu (irq_work_list, cpu)); +native_send_call_func_single_ipi (cpu);At the very leastestest make that:
if (llist_add(&work->llnode, &per_cpu(irq_work_list, cpu))) native_send_call_func_single_ipi(cpu);
Quoted 7 lines
But ideally, also test the
IRQ_WORK_LAZYsupport, its weird to have that only be supported for the other queue.Hmm, why do we need that LAZY crap, that completely wrecks a perfectly simple thing.
The changelog (
bc6679aef673f), not theprintk()usage make much sense,
s/not/nor/
Quoted 2 lines
printk()can't cause an IPI storm...printk()isn't fast enough to storm anything.
Except, as we all know, slow serial lines.
Re: [PATCH 1/3] irq_work: Implement remote queueing
In reply to Peter ZijlstraQuoted 56 lines · Peter Zijlstra
Quoted 55 lines · Frederic Weisbecker
irq work currently only supports local callbacks. However its code is mostly ready to run remote callbacks and we have some potential user.
The full nohz subsystem currently open codes its own remote irq work on top of the scheduler ipi when it wants a CPU to reevaluate its next tick. However this ad hoc solution bloats the scheduler IPI.
Lets just extend the irq work subsystem to support remote queuing on top of the generic SMP IPI to handle this kind of user. This shouldn't add noticeable overhead.
Suggested-by Peter Zijlstra <[email protected]>Cc Andrew Morton <[email protected]>Cc Ingo Molnar <[email protected]>Cc Kevin Hilman <[email protected]>Cc Paul E. McKenney <[email protected]>Cc Peter Zijlstra <[email protected]>Cc Thomas Gleixner <[email protected]>Cc Viresh Kumar <[email protected]>Signed-off-by Frederic Weisbecker <[email protected]>--- include/linux/irq_work.h | 2 ++ kernel/irq_work.c | 19 ++++++++++++++++++- kernel/smp.c | 4 ++++ 3 files changed, 24 insertions(+), 1 deletion(-)include/linux/irq_work.h +2
-0@@ -33,6 +33,8 @@ void init_irq_work(struct irq_work *work, void (*func)(struct irq_work *))#define DEFINE_IRQ_WORK (name, _f) struct irq_work name = { .func = (_f), }bool irq_work_queue (struct irq_work *work); +bool irq_work_queue_on (struct irq_work *work,int cpu); +void irq_work_run (void );void irq_work_sync (struct irq_work *work);kernel/irq_work.c +3
-1@@ -56,11 +56,28 @@ void __weak arch_irq_work_raise(void) }/* -* Enqueue the irq_work @entry unless it's already pending +* Enqueue the irq_work @work on @cpu unless it's already pending * somewhere. * * Can be re-enqueued while the callback is still in progress. */ +bool irq_work_queue_on (struct irq_work *work,int cpu) +{
Quoted 8 lines
kernel/irq_work.c void __weak arch_irq_work_raise(void) · line 71
Quoted 6 lines
kernel/irq_work.c +6
-0+/* Only queue if not already pending */ +if (!irq_work_claim (work)) +return false; + +/* All work should have been flushed before going offline */ +WARN_ON_ONCE (cpu_is_offline (cpu));WARN_ON_ONCE(in_nmi());
Well... I think it's actually NMI-safe.
Quoted 9 lines
kernel/irq_work.c void __weak arch_irq_work_raise(void) · line 74
Quoted 4 lines
kernel/irq_work.c +3
-0+ +llist_add (&work->llnode, &per_cpu (irq_work_list, cpu)); +native_send_call_func_single_ipi (cpu);At the very leastestest make that:
if (llist_add(&work->llnode, &per_cpu(irq_work_list, cpu))) native_send_call_func_single_ipi(cpu);
So yeah the issue is that we may have IRQ_WORK_LAZY in the queue. And if we have only such work in the queue, nobody has raised before us.
So we can't just test with llist_add(). Or if we do, we must then separate raised and lazy list.
Also note that nohz is the only user for now and irq_work_claim() thus prevents from double IPI. Of course if more users come up the issue arise again.
Quoted 3 lines
But ideally, also test the
IRQ_WORK_LAZYsupport, its weird to have that only be supported for the other queue.
OTOH IRQ_WORK_LAZY don't make much sense in remote queueing. We can't safely just *wait* for another CPU's tick. The IPI is necessary anyway.
Quoted 7 lines
Hmm, why do we need that LAZY crap, that completely wrecks a perfectly simple thing.
The changelog (
bc6679aef673f), not theprintk()usage make much sense,printk()can't cause an IPI storm...printk()isn't fast enough to storm anything.
Maybe I was paranoid but I was worried about the overhead of printk() wakeups on boot if implemented with IPIs.
Of course if I can be proven that it won't bring much damage to use an IPI, I'd be very happy to remove it.
Peter Zijlstra
maintainerRe: [PATCH 1/3] irq_work: Implement remote queueing
Quoted 11 lines · Frederic Weisbecker
Quoted 10 lines
kernel/irq_work.c void __weak arch_irq_work_raise(void) · line 71
Quoted 8 lines
kernel/irq_work.c +8
-0+bool irq_work_queue_on (struct irq_work *work,int cpu) +{ +/* Only queue if not already pending */ +if (!irq_work_claim (work)) +return false; + +/* All work should have been flushed before going offline */ +WARN_ON_ONCE (cpu_is_offline (cpu));WARN_ON_ONCE(in_nmi());
Quoted 1 line
Well... I think it's actually NMI-safe.
I don't think it is, most apic calls do apic_wait_icr_idle() then the apic op, if an NMI happens in between and writes to the APIC, the return context will see a !idle icr and fail.
This is why arch_irq_work_raise() again idles the icr after sending the IPI.
Also, I think, seeing what benh said earlier, its unsafe for other archs too.
Quoted 5 lines
Quoted 5 lines
kernel/irq_work.c void __weak arch_irq_work_raise(void) · line 74
Quoted 2 lines
kernel/irq_work.c +2
-0+llist_add (&work->llnode, &per_cpu (irq_work_list, cpu)); +native_send_call_func_single_ipi (cpu);At the very leastestest make that:
Quoted 8 lines
Quoted 2 lines
if (llist_add(&work->llnode, &per_cpu(irq_work_list, cpu))) native_send_call_func_single_ipi(cpu);So yeah the issue is that we may have
IRQ_WORK_LAZYin the queue. And if we have only such work in the queue, nobody has raised before us.So we can't just test with
llist_add(). Or if we do, we must then separate raised and lazy list.
Then do the remote irq_work_raised thing. But it really stinks you broke this very nice and simple thing.
Quoted 3 lines
Also note that nohz is the only user for now and
irq_work_claim()thus prevents from double IPI. Of course if more users come up the issue arise again.
DANGER, half arsed engineering at work, seriously? Just write proper code already.
There's no fucking way the next user will check the implementation to make sure its 'sane'.
Quoted 5 lines
Maybe I was paranoid but I was worried about the overhead of
printk()wakeups on boot if implemented with IPIs.Of course if I can be proven that it won't bring much damage to use an IPI, I'd be very happy to remove it.
That's the wrong fucking way around, first proof its needed then do something about it. As is I think the LAZY thing is horrid.
Re: [PATCH 1/3] irq_work: Implement remote queueing
Quoted 18 lines · Peter Zijlstra
Quoted 11 lines · Frederic Weisbecker
Quoted 10 lines
kernel/irq_work.c void __weak arch_irq_work_raise(void) · line 71
Quoted 8 lines
kernel/irq_work.c +8
-0+bool irq_work_queue_on (struct irq_work *work,int cpu) +{ +/* Only queue if not already pending */ +if (!irq_work_claim (work)) +return false; + +/* All work should have been flushed before going offline */ +WARN_ON_ONCE (cpu_is_offline (cpu));WARN_ON_ONCE(in_nmi());Quoted 1 line
Well... I think it's actually NMI-safe.
I don't think it is, most apic calls do
apic_wait_icr_idle()then the apic op, if an NMI happens in between and writes to the APIC, the return context will see a !idle icr and fail.
Quoted 5 lines
This is why
arch_irq_work_raise()again idles the icr after sending the IPI.Also, I think, seeing what benh said earlier, its unsafe for other archs too.
Ah I don't know much these archs details, so I concede it.
Quoted 9 lines
Quoted 9 lines
Quoted 8 lines
kernel/irq_work.c void __weak arch_irq_work_raise(void) · line 74
Quoted 3 lines
kernel/irq_work.c +2
-0+llist_add (&work->llnode, &per_cpu (irq_work_list, cpu)); +native_send_call_func_single_ipi (cpu);At the very leastestest make that:
if (llist_add(&work->llnode, &per_cpu(irq_work_list, cpu))) native_send_call_func_single_ipi(cpu);
Quoted 8 lines
Quoted 5 lines
So yeah the issue is that we may have
IRQ_WORK_LAZYin the queue. And if we have only such work in the queue, nobody has raised before us.So we can't just test with
llist_add(). Or if we do, we must then separate raised and lazy list.Then do the remote
irq_work_raisedthing. But it really stinks you broke this very nice and simple thing.
I tried not to break boot with printk overhead. That said I've considered having a very simple "tick work" that can rely on irq work when the tick is stopped and use it for printk. That would restore the initial simplicity.
Quoted 10 lines
Quoted 4 lines
Also note that nohz is the only user for now and
irq_work_claim()thus prevents from double IPI. Of course if more users come up the issue arise again.DANGER, half arsed engineering at work, seriously? Just write proper code already.
There's no fucking way the next user will check the implementation to make sure its 'sane'.
Are you competing with tglx on grumpiness? You guys are free to treat us like shit but don't be surprised if one day you'll be alone in kernel/*
Quoted 9 lines
Quoted 6 lines
Maybe I was paranoid but I was worried about the overhead of
printk()wakeups on boot if implemented with IPIs.Of course if I can be proven that it won't bring much damage to use an IPI, I'd be very happy to remove it.
That's the wrong fucking way around, first proof its needed then do something about it. As is I think the LAZY thing is horrid.
Peter Zijlstra
maintainerRe: [PATCH 1/3] irq_work: Implement remote queueing
Quoted 11 lines · Frederic Weisbecker
Quoted 9 lines
I don't think it is, most apic calls do
apic_wait_icr_idle()then the apic op, if an NMI happens in between and writes to the APIC, the return context will see a !idle icr and fail.This is why
arch_irq_work_raise()again idles the icr after sending the IPI.Also, I think, seeing what benh said earlier, its unsafe for other archs too.
Ah I don't know much these archs details, so I concede it.
Yeah, I didn't either, had to figure it out when someone asked WTH there was an wait_icr_idle call in there.
Quoted 6 lines
Quoted 2 lines
Then do the remote
irq_work_raisedthing. But it really stinks you broke this very nice and simple thing.I tried not to break boot with printk overhead. That said I've considered having a very simple "tick work" that can rely on irq work when the tick is stopped and use it for printk. That would restore the initial simplicity.
But but but.. did you even try without the lazy thing?
Don't fix what ain't broken, keep it simple, etc..
Anyway, if it turns out to really be needed, the split list doesn't sound bad.
Quoted 4 lines
Quoted 4 lines
Quoted 3 lines
Also note that nohz is the only user for now and
irq_work_claim()thus prevents from double IPI. Of course if more users come up the issue arise again.
Quoted 8 lines
Quoted 5 lines
DANGER, half arsed engineering at work, seriously? Just write proper code already.
There's no fucking way the next user will check the implementation to make sure its 'sane'.
Are you competing with tglx on grumpiness? You guys are free to treat us like shit but don't be surprised if one day you'll be alone in
kernel/*
There's really only so much nonsense one can take on any one day before getting seriously grumpy.
And arguing that because there's only one user so we can skimp a core function really tops the day.
So maybe I need a holiday, but shees.
Re: [PATCH 1/3] irq_work: Implement remote queueing
Quoted 19 lines · Peter Zijlstra
Quoted 11 lines · Frederic Weisbecker
Quoted 9 lines
I don't think it is, most apic calls do
apic_wait_icr_idle()then the apic op, if an NMI happens in between and writes to the APIC, the return context will see a !idle icr and fail.This is why
arch_irq_work_raise()again idles the icr after sending the IPI.Also, I think, seeing what benh said earlier, its unsafe for other archs too.
Ah I don't know much these archs details, so I concede it.
Yeah, I didn't either, had to figure it out when someone asked WTH there was an
wait_icr_idlecall in there.Quoted 3 lines
Quoted 2 lines
Then do the remote
irq_work_raisedthing. But it really stinks you broke this very nice and simple thing.
Quoted 7 lines
Quoted 3 lines
I tried not to break boot with printk overhead. That said I've considered having a very simple "tick work" that can rely on irq work when the tick is stopped and use it for printk. That would restore the initial simplicity.
But but but.. did you even try without the lazy thing?
Don't fix what ain't broken, keep it simple, etc..
The problem is that I may well see no significant issues in my small and common hardware but the problem may hit on boxes with specific configs or big numbers of CPUs.
"Don't fix what ain't broken" here clashes with "lets stay conservative/paranoid" to avoid bringing new bugs. Before printk used irq_work we had printk_tick(), I simply kept the old behaviour to avoid breaking boot time on other boxes.
Quoted 3 lines
Anyway, if it turns out to really be needed, the split list doesn't sound bad.
Either that or we can remove LAZY stuff and wait to see if people complain :)
Quoted 21 lines
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
Also note that nohz is the only user for now and
irq_work_claim()thus prevents from double IPI. Of course if more users come up the issue arise again.Quoted 8 lines
Quoted 5 lines
DANGER, half arsed engineering at work, seriously? Just write proper code already.
There's no fucking way the next user will check the implementation to make sure its 'sane'.
Are you competing with tglx on grumpiness? You guys are free to treat us like shit but don't be surprised if one day you'll be alone in
kernel/*There's really only so much nonsense one can take on any one day before getting seriously grumpy.
And arguing that because there's only one user so we can skimp a core function really tops the day.
So maybe I need a holiday, but shees.
Peter Zijlstra
maintainerRe: [PATCH 1/3] irq_work: Implement remote queueing
Quoted 4 lines · Frederic Weisbecker
Quoted 2 lines
Anyway, if it turns out to really be needed, the split list doesn't sound bad.
Either that or we can remove LAZY stuff and wait to see if people complain :)
How big do we need tested? I'm fairly sure RHT has some medium silly boxes to run things on.
Re: [PATCH 1/3] irq_work: Implement remote queueing
Quoted 8 lines · Peter Zijlstra
Quoted 4 lines · Frederic Weisbecker
Quoted 2 lines
Anyway, if it turns out to really be needed, the split list doesn't sound bad.
Either that or we can remove LAZY stuff and wait to see if people complain :)
How big do we need tested? I'm fairly sure RHT has some medium silly boxes to run things on.
Poke Davidlohr and pretend it's a futex optimization.
He has access to a 160 way for futex tests :)
Thanks,
tglx
PATCH 2/3 nohz: Move full nohz kick to its own IPI
In reply to Frederic WeisbeckerNow that the irq work subsystem can queue remote callbacks, it's a perfect fit to safely queue IPIs when interrupts are disabled without worrying about concurrent callers.
Lets use it for the full dynticks kick to notify a CPU that it's exiting single task mode.
This unbloats a bit the scheduler IPI that the nohz code was abusing for its cool "callable anywhere/anytime" properties.
--- include/linux/tick.h | 9 ++++++++- kernel/sched/core.c | 5 +---- kernel/sched/sched.h | 2 +- kernel/time/tick-sched.c | 10 ++++++---- 4 files changed, 16 insertions(+), 10 deletions(-)
include/linux/tick.h +8 -1
@@ -181,7 +181,13 @@ static inline bool tick_nohz_full_cpu(int cpu)extern void tick_nohz_init (void );extern void __tick_nohz_full_check (void ); -extern void tick_nohz_full_kick (void ); +extern void tick_nohz_full_kick_cpu (int cpu); + +static inline void tick_nohz_full_kick (void ) +{ +tick_nohz_full_kick_cpu (smp_processor_id ()); +} +extern void tick_nohz_full_kick_all (void );extern void __tick_nohz_task_switch (struct task_struct *tsk);#else
@@ -189,6 +195,7 @@ static inline void tick_nohz_init(void) { }static inline bool tick_nohz_full_enabled (void ) {return false; }static inline bool tick_nohz_full_cpu (int cpu) {return false; }static inline void __tick_nohz_full_check (void ) { } +static inline void tick_nohz_full_kick_cpu (int cpu) { }static inline void tick_nohz_full_kick (void ) { }static inline void tick_nohz_full_kick_all (void ) { }static inline void __tick_nohz_task_switch (struct task_struct *tsk) { }
kernel/sched/core.c +1 -4
@@ -1500,9 +1500,7 @@ void scheduler_ipi(void)*/ preempt_fold_need_resched (); -if (llist_empty (&this_rq ()->wake_list) - && !tick_nohz_full_cpu (smp_processor_id ()) - && !got_nohz_idle_kick ()) +if (llist_empty (&this_rq ()->wake_list) && !got_nohz_idle_kick ())return ;/*
@@ -1519,7 +1517,6 @@ void scheduler_ipi(void)* somewhat pessimize the simple resched case. */ irq_enter (); -tick_nohz_full_check ();sched_ttwu_pending ();/*
kernel/sched/sched.h +1 -1
@@ -1225,7 +1225,7 @@ static inline void inc_nr_running(struct rq *rq)if (tick_nohz_full_cpu (rq->cpu)) {/* Order rq->nr_running write against the IPI */ smp_wmb (); -smp_send_reschedule (rq->cpu); +tick_nohz_full_kick_cpu (rq->cpu); } }#endif
kernel/time/tick-sched.c +6 -4
@@ -224,13 +224,15 @@ static DEFINE_PER_CPU(struct irq_work, nohz_full_kick_work) = { };/* -* Kick the current CPU if it's full dynticks in order to force it to +* Kick the CPU if it's full dynticks in order to force it to * re-evaluate its dependency on the tick and restart it if necessary. */ -void tick_nohz_full_kick (void ) +void tick_nohz_full_kick_cpu (int cpu) { -if (tick_nohz_full_cpu (smp_processor_id ())) -irq_work_queue (&__get_cpu_var (nohz_full_kick_work)); +if (!tick_nohz_full_cpu (cpu)) +return ; + +irq_work_queue_on (&per_cpu (nohz_full_kick_work, cpu), cpu); }static void nohz_full_kick_ipi (void *info)
Signature · 1 line
1.8.3.1
PATCH 3/3 nohz: Use IPI implicit full barrier against rq->nr_running r/w
In reply to Frederic WeisbeckerA full dynticks CPU is allowed to stop its tick when a single task runs. Meanwhile when a new task gets enqueued, the CPU must be notified so that it can restart its tick to maintain local fairness and other accounting details.
This notification is performed by way of an IPI. Then when the target receives the IPI, we expect it to see the new value of rq->nr_running.
Hence the following ordering scenario:
CPU 0 CPU 1
write rq->running get IPI smp_wmb() smp_rmb() send IPI read rq->nr_running
But Paul Mckenney says that nowadays IPIs imply a full barrier on all architectures. So we can safely remove this pair and rely on the implicit barriers that come along IPI send/receive. Lets just comment on this new assumption.
--- kernel/sched/core.c | 9 +++++---- kernel/sched/sched.h | 10 ++++++++-- 2 files changed, 13 insertions(+), 6 deletions(-)
kernel/sched/core.c +5 -4
@@ -670,10 +670,11 @@ bool sched_can_stop_tick(void) rq =this_rq (); -/* Make sure rq->nr_running update is visible after the IPI */ -smp_rmb (); - -/* More than one running task need preemption */ +/* +* More than one running task need preemption. +* nr_running update is assumed to be visible +* after IPI is sent from wakers. +*/ if (rq->nr_running >1 )return false;
kernel/sched/sched.h +8 -2
@@ -1223,8 +1223,14 @@ static inline void inc_nr_running(struct rq *rq)#ifdef CONFIG_NO_HZ_FULL if (rq->nr_running ==2 ) {if (tick_nohz_full_cpu (rq->cpu)) { -/* Order rq->nr_running write against the IPI */ -smp_wmb (); +/* +* Tick is needed if more than one task runs on a CPU. +* Send the target an IPI to kick it out of nohz mode. +* +* We assume that IPI implies full memory barrier and the +* new value of rq->nr_running is visible on reception +* from the target. +*/ tick_nohz_full_kick_cpu (rq->cpu); } }
Signature · 1 line
1.8.3.1
Peter Zijlstra
maintainerRe: [PATCH 3/3] nohz: Use IPI implicit full barrier against rq->nr_running r/w
Quoted 5 lines · Frederic Weisbecker
kernel/sched/core.c +0
-1@@ -670,10 +670,11 @@ bool sched_can_stop_tick(void) rq =this_rq (); -/* Make sure rq->nr_running update is visible after the IPI */
kernel/sched/core.c bool sched_can_stop_tick(void) · line 679
Quoted 10 lines
kernel/sched/core.c +5
-3-smp_rmb (); - -/* More than one running task need preemption */ +/* +* More than one running task need preemption. +* nr_running update is assumed to be visible +* after IPI is sent from wakers. +*/ if (rq->nr_running >1 )return false;
Looks like whitespace damage on that comment's indenting.
Re: [PATCH 3/3] nohz: Use IPI implicit full barrier against rq->nr_running r/w
Quoted 5 lines · Peter Zijlstra
Quoted 4 lines · Frederic Weisbecker
kernel/sched/core.c +0
-0@@ -670,10 +670,11 @@ bool sched_can_stop_tick(void) rq =this_rq ();
Quoted 13 lines
kernel/sched/core.c bool sched_can_stop_tick(void) · line 679
Quoted 11 lines
kernel/sched/core.c +5
-4-/* Make sure rq->nr_running update is visible after the IPI */ -smp_rmb (); - -/* More than one running task need preemption */ +/* +* More than one running task need preemption. +* nr_running update is assumed to be visible +* after IPI is sent from wakers. +*/ if (rq->nr_running >1 )return false;Looks like whitespace damage on that comment's indenting.
Oops!