From: Dave Hansen <haveblue@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: How to notify app of changed cpu/mem/io node configuration?
Date: Tue, 29 Jun 2004 22:41:36 +0000 [thread overview]
Message-ID: <1088548896.23932.72.camel@nighthawk> (raw)
In-Reply-To: <20040628173808.04718b83.pj@sgi.com>
On Mon, 2004-06-28 at 23:24, Greg KH wrote:
> On Mon, Jun 28, 2004 at 05:38:08PM -0700, Paul Jackson wrote:
> > I can imagine using for notification a new signal, that could be sent by
> > an administrator or system service (batch manager, perhaps) to tasks if
> > their allowed CPUs or Memory Nodes or other such had changed.
>
> I recall some initial proposals for when CPUs were offlined, to send the
> applications that were bound to those CPUs a specific signal, but I do
> not know if that got implemented or not. Anyone know?
I don't see anything in the various signal.h files that looks likely.
But, we'll probably need some kind of synchronous process notification
at some point. If an app gets itself in a bad state such that it has no
possibility of being scheduled, or gets itself into some other hopeless
state due to a hotplug action, the kernel will likely have the option to
kill it.
I think the problem for the kernel comes when we consider how to notify
the app. Doing a hotplug event and having the scripts send an
appropriate signal isn't really a viable option because the kernel
wouldn't really know when each app had a chance to handle the signal.
Sleeping for 5 seconds and hoping for the best probably isn't the best
option, either. :)
The other option would be to have the kernel send signals to the
processes, and recheck the "impossible state" after the signal has been
handled.
I don't really remember how the discussions about CPU hotplug ended, but
I wonder if a much more generic signal could be of more use than a
single task CPU hotplug signal.
What about a SIGHOTPLUG that can be used whenever the kernel notices
that a task is using a resource that's being hotplugged?
-- Dave
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-06-29 22:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 0:38 How to notify app of changed cpu/mem/io node configuration? Paul Jackson
2004-06-29 6:24 ` Greg KH
2004-06-29 8:37 ` Paul Jackson
2004-06-29 22:41 ` Dave Hansen [this message]
2004-06-29 23:15 ` Paul Jackson
2004-06-29 23:39 ` Dave Hansen
2004-06-29 23:53 ` Rusty Russell
2004-06-30 1:22 ` Paul Jackson
2004-06-30 1:38 ` Dave Hansen
2004-06-30 1:40 ` Paul Jackson
2004-06-30 2:16 ` Paul Jackson
2004-06-30 11:57 ` jlm_devel
2004-06-30 12:26 ` Paul Jackson
2004-06-30 13:08 ` Paul Jackson
2004-06-30 17:37 ` jlm_devel
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=1088548896.23932.72.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).