From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Tim Hockin <thockin@hockin.org>
Cc: Nick Piggin <piggin@cyberone.com.au>,
Rusty Russell <rusty@au1.ibm.com>,
linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org,
rml@tech9.net
Subject: Re: CPU Hotplug: Hotplug Script And SIGPWR
Date: Wed, 21 Jan 2004 09:36:33 +0530 [thread overview]
Message-ID: <20040121093633.A3169@in.ibm.com> (raw)
In-Reply-To: <20040120084352.GD15733@hockin.org>; from thockin@hockin.org on Tue, Jan 20, 2004 at 12:43:52AM -0800
On Tue, Jan 20, 2004 at 12:43:52AM -0800, Tim Hockin wrote:
> IFF the app is designed to handle it. The existence of a SIGPWR handler
> does not necessarily imply that, though. a SIGCPU or something might
> correlate 1:1 with this, but SIGPWR doesn't.
I agree we should have a separe signal for CPU Hotplug. By default the signal
will be ignored, unless a task registers a signal handler for that special
signal.
That way, tasks which "knowingly" change their CPU affinity will be able to
tackle a CPU going down by handling the signal (probably change their CPU
affinity again), while tasks which have their CPU affinity changed "unknowingly"
(by other tasks) will just ignore the signal. The hotplug script interface
allows the admin to go and change the CPU affinity again for the second class
of tasks, if needed.
The only problem with a new signal is conformance to standards (if any).
--
Thanks and Regards,
Srivatsa Vaddagiri,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560017
next prev parent reply other threads:[~2004-01-21 4:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040116174446.A2820@in.ibm.com>
2004-01-20 5:44 ` CPU Hotplug: Hotplug Script And SIGPWR Rusty Russell
2004-01-20 6:33 ` Tim Hockin
2004-01-20 6:43 ` Nick Piggin
2004-01-20 6:52 ` Tim Hockin
2004-01-20 7:11 ` Nick Piggin
2004-01-20 7:30 ` Tim Hockin
2004-01-20 7:45 ` Nick Piggin
2004-01-20 7:54 ` Tim Hockin
2004-01-20 8:14 ` Nick Piggin
2004-01-20 8:29 ` Tim Hockin
2004-01-20 8:37 ` Nick Piggin
2004-01-20 8:43 ` Tim Hockin
2004-01-21 4:06 ` Srivatsa Vaddagiri [this message]
2004-01-21 4:14 ` Nick Piggin
2004-01-21 5:09 ` Srivatsa Vaddagiri
2004-01-21 7:08 ` Tim Hockin
2004-01-21 15:07 ` Matthias Urlichs
2004-01-22 5:29 ` Rusty Russell
2004-01-21 7:09 ` Tim Hockin
2004-01-21 7:31 ` Nick Piggin
2004-01-21 7:42 ` Tim Hockin
2004-01-21 8:11 ` Rusty Russell
2004-01-21 5:07 ` Rusty Russell
2004-01-20 8:41 ` Stefan Smietanowski
2004-01-20 8:49 ` Nick Piggin
2004-01-20 9:12 ` Tim Hockin
2004-01-21 0:00 ` Rusty Russell
2004-01-20 23:51 ` Rusty Russell
2004-01-20 7:45 ` Rusty Russell
2004-01-20 8:37 ` Tim Hockin
2004-01-20 9:29 ` Srivatsa Vaddagiri
2004-01-21 0:12 ` Rusty Russell
[not found] <fa.f37o48p.1io5q5@ifi.uio.no>
[not found] ` <fa.frjqvfo.170g8hq@ifi.uio.no>
2004-01-20 17:49 ` Andy Lutomirski
2004-01-21 4:33 ` Rusty Russell
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=20040121093633.A3169@in.ibm.com \
--to=vatsa@in.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
--cc=rml@tech9.net \
--cc=rusty@au1.ibm.com \
--cc=thockin@hockin.org \
--cc=torvalds@osdl.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