From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Oleg Nesterov <oleg@tv-sign.ru>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [RFC] Thread Migration Preemption - v4
Date: Sat, 14 Jul 2007 21:14:11 +0200 [thread overview]
Message-ID: <1184440451.5284.75.camel@lappy> (raw)
In-Reply-To: <20070714184237.GI6975@Krystal>
Would have been nice if you'd CC'ed me :-/
On Sat, 2007-07-14 at 14:42 -0400, Mathieu Desnoyers wrote:
> @@ -4891,10 +4948,42 @@ static int migration_thread(void *data)
> list_del_init(head->next);
>
> spin_unlock(&rq->lock);
> - __migrate_task(req->task, cpu, req->dest_cpu);
> + migrated = __migrate_task(req->task, cpu, req->dest_cpu);
> local_irq_enable();
> -
> - complete(&req->done);
> + if (!migrated) {
> + /*
> + * If the process has not been migrated, let it run
> + * until it reaches a migration_check() so it can
> + * wake us up.
> + */
> + spin_lock_irq(&rq->lock);
> + head = &rq->migration_queue;
> + list_add(&req->list, head);
> + if (req->task->se.on_rq
> + || !task_migrate_count(req->task)) {
> + /*
> + * The process is on the runqueue, it could
> + * exit its critical section at any moment,
> + * don't race with it and retry actively.
> + * Also, if the thread is not on the runqueue
> + * and has a zero migration count
> + * (__migrate_task failed because cpus allowed
> + * changed), just retry.
> + */
> + spin_unlock_irq(&rq->lock);
> + continue;
> + }
> + set_tsk_thread_flag(req->task, TIF_NEED_MIGRATE);
> + set_current_state(TASK_INTERRUPTIBLE);
> + spin_unlock_irq(&rq->lock);
> + /*
> + * Wait for the process currently in its critical
> + * section.
> + */
> + wake_up_process(req->task);
> + schedule();
> + } else
> + complete(&req->done);
> }
> __set_current_state(TASK_RUNNING);
> return 0;
I'm not really liking this, this way we hold up all other migration
requests.
next prev parent reply other threads:[~2007-07-14 19:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 6:02 [RFC] Thread Migration Preemption Oleg Nesterov
2007-07-06 14:23 ` Mathieu Desnoyers
2007-07-06 14:56 ` Oleg Nesterov
2007-07-11 4:49 ` [RFC] Thread Migration Preemption - v2 Mathieu Desnoyers
2007-07-11 16:36 ` Oleg Nesterov
2007-07-14 18:27 ` Mathieu Desnoyers
2007-07-14 19:56 ` Oleg Nesterov
2007-07-14 18:40 ` [RFC] Thread Migration Preemption - v3 Mathieu Desnoyers
2007-07-14 18:42 ` [RFC] Thread Migration Preemption - v4 Mathieu Desnoyers
2007-07-14 19:14 ` Peter Zijlstra [this message]
2007-07-14 20:25 ` Mathieu Desnoyers
2007-07-14 19:30 ` Peter Zijlstra
2007-07-14 20:26 ` Mathieu Desnoyers
2007-07-14 20:23 ` Oleg Nesterov
2007-07-14 20:33 ` Mathieu Desnoyers
2007-07-14 20:42 ` Oleg Nesterov
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=1184440451.5284.75.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=rostedt@goodmis.org \
/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