LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Clark Williams" <williams@redhat.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
"Mike Galbraith" <umgwanakikbuti@gmail.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"Jörn Engel" <joern@purestorage.com>
Subject: Re: [RFC][PATCH v2] sched/rt: Use IPI to trigger RT task push migration instead of pulling
Date: Wed, 25 Feb 2015 18:41:57 +0100 [thread overview]
Message-ID: <20150225174157.GX24151@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150225171110.GO21418@twins.programming.kicks-ass.net>
On Wed, Feb 25, 2015 at 06:11:10PM +0100, Peter Zijlstra wrote:
>
> #define IPS_BUSY 0x01
> #define IPS_LOOPED 0x02
>
> struct ipi_pull_struct {
> struct irq_work work;
> raw_spinlock_t lock;
> int flags;
> int dst_cpu; /* CPU that issued this search */
> int dst_prio; /* Prio of the originating CPU */
> int src_cpu; /* CPU where the IPI is running */
> int stop_cpu; /* cpu where we can stop iterating */
> ...
> };
>
> Where you can increase seq every time you change it and the IPI will
> continue at least one more rto mask round for every change?
seq got lost.. ignore that bit, look at the code.
> int ips_next(struct ipi_pull_struct *ips)
> {
> int cpu = ips->src_cpu;
> cpu = cpumask_next(cpu, rto_mask);
> if (cpu >= nr_cpu_ids) {
> cpu = 0;
should be -1
> ips->flags |= IPS_LOOPED;
> cpu = cpumask_next(cpu, rto_mask);
> if (cpu >= nr_cpu_ids) /* empty mask *;
> return cpu;
> }
> if (ips->flags & IPS_LOOPED && cpu >= ips->stop_cpu)
> return nr_cpu_ids;
> return cpu;
> }
>
>
>
> struct ipi_pull_struct *ips = __this_cpu_ptr(ips);
>
> raw_spin_lock(&ips->lock);
> if (ips->flags & IPS_BUSY) {
> /* there is an IPI active; update state */
> ips->dst_prio = current->prio;
> ips->stop_cpu = ips->src_cpu;
> ips->flags &= ~IPS_LOOPED;
> } else {
> /* no IPI active, make one go */
> ips->dst_cpu = smp_processor_id();
> ips->dst_prio = current->prio;
> ips->src_cpu = ips->dst_cpu;
> ips->stop_cpu = ips->dst_cpu;
> ips->flags = IPS_BUSY;
>
> cpu = ips_next(ips);
> ips->src_cpu = cpu;
> if (cpu < nr_cpu_ids)
> irq_work_queue_on(&ips->work, cpu);
> }
> raw_spin_unlock(&ips->lock);
There might be a wee race vs the busy looping, seeing how src_cpu might
be checking against the old dst_prio, so we could check one too few rto
mask.
No real problem I think.
next prev parent reply other threads:[~2015-02-25 17:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 18:39 Steven Rostedt
2015-02-24 18:45 ` Steven Rostedt
2015-02-24 21:23 ` Steven Rostedt
2015-02-25 10:35 ` Peter Zijlstra
2015-02-25 15:51 ` Steven Rostedt
2015-02-25 17:11 ` Peter Zijlstra
2015-02-25 17:41 ` Peter Zijlstra [this message]
2015-02-25 17:50 ` Steven Rostedt
2015-02-26 7:45 ` Peter Zijlstra
2015-02-26 12:43 ` Steven Rostedt
2015-02-26 13:47 ` Peter Zijlstra
2015-02-26 14:00 ` Steven Rostedt
2015-02-26 7:49 ` Peter Zijlstra
2015-02-26 12:46 ` Steven Rostedt
2015-02-25 7:56 Hillf Danton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150225174157.GX24151@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=joern@purestorage.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
--cc=williams@redhat.com \
--subject='Re: [RFC][PATCH v2] sched/rt: Use IPI to trigger RT task push migration instead of pulling' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).