From: Pavel Machek <pavel@suse.cz>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
clameter@sgi.com, ntl@pobox.com, akpm@osdl.org,
linux-kernel@vger.kernel.org, ashok.raj@intel.com, ak@suse.de,
nickpiggin@yahoo.com.au, mingo@elte.hu
Subject: Re: [PATCH] stop on cpu lost
Date: Thu, 22 Jun 2006 20:22:31 +0200 [thread overview]
Message-ID: <20060622182231.GC4193@elf.ucw.cz> (raw)
In-Reply-To: <20060622092422.256d6692.rdunlap@xenotime.net>
Hi!
> > Hm..
> > Then, there is several ways to manage this sitation.
> >
> > 1. migrate all even if it's not allowed by users
That's what I'd prefer... as swsusp uses cpu hotplug. All the other
options are bad... admin will probably not realize suspend involves
cpu unplugs..
> > 2. kill mis-configured tasks.
> > 3. stop ...
> > 4. cancel cpu-hot-removal.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-06-22 18:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 3:51 [PATCH] stop on cpu lost KAMEZAWA Hiroyuki
2006-06-22 5:56 ` Andrew Morton
2006-06-22 6:14 ` Christoph Lameter
2006-06-22 15:08 ` Nathan Lynch
2006-06-22 15:45 ` Randy.Dunlap
2006-06-22 15:45 ` Christoph Lameter
2006-06-22 16:05 ` KAMEZAWA Hiroyuki
2006-06-22 16:14 ` Christoph Lameter
2006-06-22 16:24 ` Randy.Dunlap
2006-06-22 17:04 ` Nathan Lynch
2006-06-22 17:20 ` KAMEZAWA Hiroyuki
2006-06-22 18:22 ` Pavel Machek [this message]
2006-06-22 18:35 ` Christoph Lameter
2006-06-22 18:37 ` Pavel Machek
2006-06-22 18:54 ` Hugh Dickins
2006-06-22 19:27 ` Nick Piggin
2006-06-22 19:46 ` Hugh Dickins
2006-06-22 19:57 ` Nick Piggin
2006-06-22 20:25 ` Hugh Dickins
2006-06-22 21:44 ` Pavel Machek
2006-06-22 19:52 ` Jeremy Fitzhardinge
2006-06-22 21:46 ` Pavel Machek
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=20060622182231.GC4193@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=clameter@sgi.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=ntl@pobox.com \
--cc=rdunlap@xenotime.net \
/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