From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Clark Williams <williams@redhat.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
John Kacur <jkacur@redhat.com>, Scott Wood <swood@redhat.com>
Subject: Re: [PATCH tip/sched/core v2] sched/rt: Simplify the IPI rt balancing logic
Date: Thu, 4 May 2017 17:32:56 +0200 [thread overview]
Message-ID: <20170504153256.fbmglqe2zjo6ika2@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20170424114732.1aac6dc4@gandalf.local.home>
On Mon, Apr 24, 2017 at 11:47:32AM -0400, Steven Rostedt wrote:
> static int rto_next_cpu(struct rq *rq)
> {
> int cpu;
>
> /*
> + * When starting the IPI RT pushing, the rto_cpu is set to nr_cpu_ids
> + * or greater. rt_next_cpu() will simply return the first CPU found in
> + * the rto_mask.
> + *
> + * If rto_next_cpu() is called with rto_cpu less than nr_cpu_ids, it
> + * will return the next CPU found in the rto_mask.
> + *
> + * If there are no more CPUs left in the rto_mask, then a check is made
> + * against rto_loop and rto_loop_next. rto_loop is only updated with
> + * the rto_lock held, but any CPU may increment the rto_loop_next
> + * without any locking.
> */
> +again:
> + if (rq->rd->rto_cpu >= nr_cpu_ids) {
> cpu = cpumask_first(rq->rd->rto_mask);
> + rq->rd->rto_cpu = cpu;
> + /* If cpu is nr_cpu_ids, then there is no overloaded rqs */
> + return cpu;
> }
>
> + cpu = cpumask_next(rq->rd->rto_cpu, rq->rd->rto_mask);
> + rq->rd->rto_cpu = cpu;
>
> + if (cpu < nr_cpu_ids)
> + return cpu;
>
> + if (rq->rd->rto_loop == atomic_read(&rq->rd->rto_loop_next))
> + return cpu;
>
> + rq->rd->rto_loop = atomic_read(&rq->rd->rto_loop_next);
> + goto again;
> +}
I think you want to write that as:
struct root_domain *rd = rq->rd;
int cpu, next;
/* comment */
for (;;) {
if (rd->rto_cpu >= nr_cpu_ids) {
cpu = cpumask_first(rd->rto_mask);
rd->rto_cpu = cpu;
return cpu;
}
cpu = cpumask_next(rd->rto_mask);
rd->rto_cpu = cpu;
if (cpu < nr_cpu_ids)
break;
// rd->rto_cpu = -1;
/*
* ACQUIRE ensures we see the @rto_mask changes
* made prior to the @next value observed.
*
* Matches WMB in rt_set_overload().
*/
next = atomic_read_acquire(&rd->rto_loop_next);
if (rd->rto_loop == next)
break;
rd->rto_loop = next;
}
return cpu;
And I don't fully understand the whole rto_cpu >= nr_cpus_ids thing,
can't you simply reset the thing to -1 and always use cpumask_next()?
As per the // comment above?
> +static inline bool rto_start_trylock(atomic_t *v)
> +{
> + return !atomic_cmpxchg(v, 0, 1);
Arguably this could be: !atomic_cmpxchg_acquire(v, 0, 1);
> }
>
> +static inline void rto_start_unlock(atomic_t *v)
> +{
> + atomic_set_release(v, 0);
> +}
>
> static void tell_cpu_to_push(struct rq *rq)
> {
> + int cpu = nr_cpu_ids;
>
> + /* Keep the loop going if the IPI is currently active */
> + atomic_inc_return(&rq->rd->rto_loop_next);
Since rt_set_overload() already provides a WMB, we don't need an
ordered primitive here and atomic_inc() is fine.
>
> + /* Only one CPU can initiate a loop at a time */
> + if (!rto_start_trylock(&rq->rd->rto_loop_start))
> return;
>
> + raw_spin_lock(&rq->rd->rto_lock);
> +
> + /*
> + * The rto_cpu is updated under the lock, if it has a valid cpu
> + * then the IPI is still running and will continue due to the
> + * update to loop_next, and nothing needs to be done here.
> + * Otherwise it is finishing up and an ipi needs to be sent.
> + */
> + if (rq->rd->rto_cpu >= nr_cpu_ids)
// if (rq->rd->rto_cpu < 0)
> + cpu = rto_next_cpu(rq);
>
> + raw_spin_unlock(&rq->rd->rto_lock);
> +
> + rto_start_unlock(&rq->rd->rto_loop_start);
> +
> + if (cpu < nr_cpu_ids)
> + irq_work_queue_on(&rq->rd->rto_push_work, cpu);
> }
>
> /* Called from hardirq context */
> +void rto_push_irq_work_func(struct irq_work *work)
> {
> + struct rq *rq;
> int this_cpu;
> int cpu;
>
> + this_cpu = smp_processor_id();
> rq = cpu_rq(this_cpu);
rq = this_rq();
>
> + /*
> + * We do not need to grab the lock to check for has_pushable_tasks.
> + * When it gets updated, a check is made if a push is possible.
> + */
> if (has_pushable_tasks(rq)) {
> raw_spin_lock(&rq->lock);
> + push_rt_tasks(rq);
> raw_spin_unlock(&rq->lock);
> }
>
> + raw_spin_lock(&rq->rd->rto_lock);
>
> + /* Pass the IPI to the next rt overloaded queue */
> + cpu = rto_next_cpu(rq);
>
> + raw_spin_unlock(&rq->rd->rto_lock);
>
> if (cpu >= nr_cpu_ids)
> return;
>
> /* Try the next RT overloaded CPU */
> + irq_work_queue_on(&rq->rd->rto_push_work, cpu);
> }
next prev parent reply other threads:[~2017-05-04 15:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 15:47 Steven Rostedt
2017-05-04 14:41 ` Peter Zijlstra
2017-05-04 15:01 ` Steven Rostedt
2017-05-04 15:32 ` Peter Zijlstra [this message]
2017-05-04 17:25 ` Steven Rostedt
2017-05-04 18:42 ` Peter Zijlstra
2017-05-04 19:03 ` Steven Rostedt
2017-05-05 4:26 ` Mike Galbraith
2017-05-05 5:16 ` Mike Galbraith
2017-05-05 11:05 ` Peter Zijlstra
2017-05-05 12:02 ` Steven Rostedt
2017-05-05 17:39 ` Peter Zijlstra
2017-05-05 18:59 ` Steven Rostedt
2017-05-06 7:52 ` Peter Zijlstra
2017-10-10 11:02 ` [tip:sched/core] sched/rt: Simplify the IPI based RT " tip-bot for Steven Rostedt (Red Hat)
2018-01-19 9:23 ` Pavan Kondeti
2018-01-19 15:03 ` Steven Rostedt
2018-01-19 15:44 ` Pavan Kondeti
2018-01-19 15:53 ` Steven Rostedt
2018-01-19 17:46 ` Pavan Kondeti
2018-01-19 18:11 ` Steven Rostedt
2018-01-19 18:12 ` Steven Rostedt
2018-01-19 18:57 ` Pavan Kondeti
2018-01-19 19:51 ` Steven Rostedt
2018-01-20 4:56 ` Pavan Kondeti
2018-01-19 18:54 ` Pavan Kondeti
2018-02-06 11:54 ` [tip:sched/urgent] sched/rt: Use container_of() to get root domain in rto_push_irq_work_func() tip-bot for Steven Rostedt (VMware)
2018-02-07 4:14 ` Steven Rostedt
2018-02-06 11:54 ` [tip:sched/urgent] sched/rt: Up the root domain ref count when passing it around via IPIs tip-bot for Steven Rostedt (VMware)
2018-02-07 4:15 ` Steven Rostedt
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=20170504153256.fbmglqe2zjo6ika2@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=swood@redhat.com \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®