From: Pavel Machek <pavel@ucw.cz>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>, ashok.raj@intel.com
Subject: Re: [RFC][PATCH] avoid cpu hot remove of cpus which have special RT tasks.
Date: Sun, 18 Jun 2006 18:46:55 +0200 [thread overview]
Message-ID: <20060618164654.GA826@openzaurus.ucw.cz> (raw)
In-Reply-To: <20060616162343.02c3ce62.kamezawa.hiroyu@jp.fujitsu.com>
Hi!
> When cpu hot remove happens, tasks on the target cpu will be migrated even if
> no available cpus in tsk->cpus_allowed. (See: move_task_off_dead_cpu().)
>
> Usually, it looks ok (I think not good but may be ok.) But forced migration
> should be avoided if there is RT task which is designed to run only on
> specified cpu.
That would break software suspend, sorry.
NAK.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2006-06-18 21:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 7:23 KAMEZAWA Hiroyuki
2006-06-16 9:14 ` Andi Kleen
2006-06-16 10:26 ` KAMEZAWA Hiroyuki
2006-06-16 10:36 ` Andi Kleen
2006-06-16 10:58 ` KAMEZAWA Hiroyuki
2006-06-16 11:20 ` Andi Kleen
2006-06-16 11:25 ` KAMEZAWA Hiroyuki
2006-06-17 3:46 ` Nick Piggin
2006-06-17 5:12 ` KAMEZAWA Hiroyuki
2006-06-17 7:29 ` Nick Piggin
2006-06-17 7:53 ` KAMEZAWA Hiroyuki
2006-06-17 8:48 ` Nick Piggin
2006-06-17 8:58 ` KAMEZAWA Hiroyuki
2006-06-16 16:09 ` Christoph Lameter
2006-06-16 16:46 ` KAMEZAWA Hiroyuki
2006-06-16 17:29 ` Ashok Raj
2006-06-16 23:47 ` KAMEZAWA Hiroyuki
2006-06-18 16:46 ` Pavel Machek [this message]
2006-06-19 1:12 ` KAMEZAWA Hiroyuki
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=20060618164654.GA826@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=ashok.raj@intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®