From: Kirill Tkhai <ktkhai@parallels.com>
To: <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Paul Turner <pjt@google.com>, Oleg Nesterov <oleg@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
"Mike Galbraith" <umgwanakikbuti@gmail.com>,
Kirill Tkhai <tkhai@yandex.ru>,
"Tim Chen" <tim.c.chen@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
"Nicolas Pitre" <nicolas.pitre@linaro.org>
Subject: [PATCH v5 3/5] sched: Remove double_rq_lock() from __migrate_task()
Date: Wed, 20 Aug 2014 13:47:50 +0400 [thread overview]
Message-ID: <1408528070.23412.89.camel@tkhai> (raw)
In-Reply-To: <20140820092458.27076.30955.stgit@tkhai>
Avoid double_rq_lock() and use TASK_ON_RQ_MIGRATING for __migrate_task().
The advantage is (obviously) not holding two 'rq->lock's at the same time
and thereby increasing parallelism.
The important point to note is that because we acquire dst->lock
immediately after releasing src->lock the potential wait time of
task_rq_lock() callers on TASK_ON_RQ_MIGRATING is not longer than it would
have been in the double rq lock scenario.
Signed-off-by: Kirill Tkhai <ktkhai@parallels.com>
---
kernel/sched/core.c | 23 +++++++++++++++--------
1 file changed, 15 insertions(+), 8 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index cef1a13..a50393b 100644
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -4663,20 +4663,20 @@ EXPORT_SYMBOL_GPL(set_cpus_allowed_ptr);
*/
static int __migrate_task(struct task_struct *p, int src_cpu, int dest_cpu)
{
- struct rq *rq_dest, *rq_src;
+ struct rq *rq;
int ret = 0;
if (unlikely(!cpu_active(dest_cpu)))
return ret;
- rq_src = cpu_rq(src_cpu);
- rq_dest = cpu_rq(dest_cpu);
+ rq = cpu_rq(src_cpu);
raw_spin_lock(&p->pi_lock);
- double_rq_lock(rq_src, rq_dest);
+ raw_spin_lock(&rq->lock);
/* Already moved. */
if (task_cpu(p) != src_cpu)
goto done;
+
/* Affinity changed (again). */
if (!cpumask_test_cpu(dest_cpu, tsk_cpus_allowed(p)))
goto fail;
@@ -4686,15 +4686,22 @@ static int __migrate_task(struct task_struct *p, int src_cpu, int dest_cpu)
* placed properly.
*/
if (task_on_rq_queued(p)) {
- dequeue_task(rq_src, p, 0);
+ dequeue_task(rq, p, 0);
+ p->on_rq = TASK_ON_RQ_MIGRATING;
set_task_cpu(p, dest_cpu);
- enqueue_task(rq_dest, p, 0);
- check_preempt_curr(rq_dest, p, 0);
+ raw_spin_unlock(&rq->lock);
+
+ rq = cpu_rq(dest_cpu);
+ raw_spin_lock(&rq->lock);
+ BUG_ON(task_rq(p) != rq);
+ p->on_rq = TASK_ON_RQ_QUEUED;
+ enqueue_task(rq, p, 0);
+ check_preempt_curr(rq, p, 0);
}
done:
ret = 1;
fail:
- double_rq_unlock(rq_src, rq_dest);
+ raw_spin_unlock(&rq->lock);
raw_spin_unlock(&p->pi_lock);
return ret;
}
next prev parent reply other threads:[~2014-08-20 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140820092458.27076.30955.stgit@tkhai>
2014-08-20 9:47 ` [PATCH v5 1/5] sched: Wrapper for checking task_struct::on_rq Kirill Tkhai
2014-08-20 18:45 ` [tip:sched/core] sched: Add wrapper for checking task_struct:: on_rq tip-bot for Kirill Tkhai
2014-08-20 9:47 ` [PATCH v5 2/5] sched: Teach scheduler to understand TASK_ON_RQ_MIGRATING state Kirill Tkhai
2014-08-20 18:45 ` [tip:sched/core] " tip-bot for Kirill Tkhai
2014-08-20 9:47 ` Kirill Tkhai [this message]
2014-08-20 18:46 ` [tip:sched/core] sched: Remove double_rq_lock() from __migrate_task() tip-bot for Kirill Tkhai
2014-08-20 9:48 ` [PATCH v5 4/5] sched/fair: Remove double_lock_balance() from active_load_balance_cpu_stop() Kirill Tkhai
2014-08-20 18:46 ` [tip:sched/core] " tip-bot for Kirill Tkhai
2014-08-20 9:48 ` [PATCH v5 5/5] sched/fair: Remove double_lock_balance() from load_balance() Kirill Tkhai
2014-08-20 18:46 ` [tip:sched/core] " tip-bot for 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=1408528070.23412.89.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
Powered by JetHome