From: Kirill Tkhai <ktkhai@parallels.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: <linux-kernel@vger.kernel.org>, <pjt@google.com>,
<oleg@redhat.com>, <rostedt@goodmis.org>,
<umgwanakikbuti@gmail.com>, <tkhai@yandex.ru>,
<tim.c.chen@linux.intel.com>, <mingo@kernel.org>,
<nicolas.pitre@linaro.org>
Subject: Re: [PATCH v4 3/6] sched: Teach scheduler to understand ONRQ_MIGRATING state
Date: Tue, 12 Aug 2014 12:34:23 +0400 [thread overview]
Message-ID: <1407832463.23412.2.camel@tkhai> (raw)
In-Reply-To: <20140812075523.GN9918@twins.programming.kicks-ass.net>
В Вт, 12/08/2014 в 09:55 +0200, Peter Zijlstra пишет:
> On Wed, Aug 06, 2014 at 12:06:19PM +0400, Kirill Tkhai wrote:
> > --- a/kernel/sched/core.c
> > +++ b/kernel/sched/core.c
> > @@ -331,9 +331,13 @@ static inline struct rq *__task_rq_lock(struct task_struct *p)
> > lockdep_assert_held(&p->pi_lock);
> >
> > for (;;) {
> > + while (unlikely(task_migrating(p)))
> > + cpu_relax();
> > +
> > rq = task_rq(p);
> > raw_spin_lock(&rq->lock);
> > - if (likely(rq == task_rq(p)))
> > + if (likely(rq == task_rq(p) &&
> > + !task_migrating(p)))
> > return rq;
> > raw_spin_unlock(&rq->lock);
> > }
> > @@ -349,10 +353,14 @@ static struct rq *task_rq_lock(struct task_struct *p, unsigned long *flags)
> > struct rq *rq;
> >
> > for (;;) {
> > + while (unlikely(task_migrating(p)))
> > + cpu_relax();
> > +
> > raw_spin_lock_irqsave(&p->pi_lock, *flags);
> > rq = task_rq(p);
> > raw_spin_lock(&rq->lock);
> > - if (likely(rq == task_rq(p)))
> > + if (likely(rq == task_rq(p) &&
> > + !task_migrating(p)))
> > return rq;
> > raw_spin_unlock(&rq->lock);
> > raw_spin_unlock_irqrestore(&p->pi_lock, *flags);
>
> I know I suggested that; but I changed it like the below. The advantage
> is of not having two task_migrating() tests on the likely path.
I don't have objections. Should I resend the series (also with new [4/6] log
commentary)?
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -331,15 +331,15 @@ static inline struct rq *__task_rq_lock(
> lockdep_assert_held(&p->pi_lock);
>
> for (;;) {
> - while (unlikely(task_migrating(p)))
> - cpu_relax();
> -
> rq = task_rq(p);
> raw_spin_lock(&rq->lock);
> if (likely(rq == task_rq(p) &&
> !task_migrating(p)))
> return rq;
> raw_spin_unlock(&rq->lock);
> +
> + while (unlikely(task_migrating(p)))
> + cpu_relax();
> }
> }
>
> @@ -353,9 +353,6 @@ static struct rq *task_rq_lock(struct ta
> struct rq *rq;
>
> for (;;) {
> - while (unlikely(task_migrating(p)))
> - cpu_relax();
> -
> raw_spin_lock_irqsave(&p->pi_lock, *flags);
> rq = task_rq(p);
> raw_spin_lock(&rq->lock);
> @@ -364,6 +361,9 @@ static struct rq *task_rq_lock(struct ta
> return rq;
> raw_spin_unlock(&rq->lock);
> raw_spin_unlock_irqrestore(&p->pi_lock, *flags);
> +
> + while (unlikely(task_migrating(p)))
> + cpu_relax();
> }
> }
>
next prev parent reply other threads:[~2014-08-12 8:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140806075138.24858.23816.stgit@tkhai>
2014-08-06 8:06 ` [PATCH v4 1/6] sched/fair: Fix reschedule which is generated on throttled cfs_rq Kirill Tkhai
2014-08-20 8:20 ` [tip:sched/core] " tip-bot for Kirill Tkhai
2014-10-23 23:27 ` [PATCH v4 1/6] " Wanpeng Li
2014-10-24 6:01 ` Kirill Tkhai
2014-10-24 9:32 ` Wanpeng Li
2014-10-24 15:12 ` Kirill Tkhai
2014-08-06 8:06 ` [PATCH v4 2/6] sched: Wrapper for checking task_struct::on_rq Kirill Tkhai
2014-08-20 7:52 ` Ingo Molnar
2014-08-06 8:06 ` [PATCH v4 3/6] sched: Teach scheduler to understand ONRQ_MIGRATING state Kirill Tkhai
2014-08-12 7:55 ` Peter Zijlstra
2014-08-12 8:34 ` Kirill Tkhai [this message]
2014-08-12 9:43 ` Peter Zijlstra
2014-08-06 8:06 ` [PATCH v4 4/6] sched: Remove double_rq_lock() from __migrate_task() Kirill Tkhai
2014-08-12 8:21 ` Peter Zijlstra
2014-08-06 8:06 ` [PATCH v4 5/6] sched/fair: Remove double_lock_balance() from active_load_balance_cpu_stop() Kirill Tkhai
2014-08-12 9:03 ` Peter Zijlstra
2014-08-12 9:22 ` Peter Zijlstra
2014-08-12 9:39 ` Kirill Tkhai
2014-08-06 8:07 ` [PATCH v4 6/6] sched/fair: Remove double_lock_balance() from load_balance() Kirill Tkhai
2014-08-12 9:36 ` Peter Zijlstra
2014-08-12 10:27 ` Kirill Tkhai
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=1407832463.23412.2.camel@tkhai \
--to=ktkhai@parallels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rostedt@goodmis.org \
--cc=tim.c.chen@linux.intel.com \
--cc=tkhai@yandex.ru \
--cc=umgwanakikbuti@gmail.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