mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Lameter <clameter@sgi.com>
To: Pavel Machek <pavel@suse.cz>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.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 11:35:08 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0606221132040.30182@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20060622182231.GC4193@elf.ucw.cz>

On Thu, 22 Jun 2006, Pavel Machek wrote:

> > > 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..

You probably first suspend a process? If a process was suspended by 
swsusp then we can just ignore the restriction because it will be 
returned later.

The admin wants the system to behave in a consistent way. If he suddenly 
finds a process running on a cpu that was forbidden then that is weird 
and surprising to say the least and may go undetected for a long time.
If the process gets killed when he disables the cpu then he will have to 
fix up his cpu restrictions.




  reply	other threads:[~2006-06-22 18:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20  3:51 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
2006-06-22 18:35               ` Christoph Lameter [this message]
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=Pine.LNX.4.64.0606221132040.30182@schroedinger.engr.sgi.com \
    --to=clameter@sgi.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=ashok.raj@intel.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=pavel@suse.cz \
    --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

all inboxes | Powered by JetHome®