Re: CPU Hotplug: Hotplug Script And SIGPWR

Tim Hockin
2004-01-20T08:44:14Z

On Tue, Jan 20, 2004 at 07:37:48PM +1100, Nick Piggin wrote:
> (or OOM killed being another that comes to mind)
>
> It is sometimes inevitable. With that knowledge we should be designing
> for graceful failure.

Don't get me started on OOM killer. If the OOM killer is killing hotplug
scripts, there's another problem. What's the chance of hotplug scripts
being the memory hog? :)

That said, I understand what you're saying. It's rough.

> >But it is a violation of the affinity. As the kernel we CAN NOT know what
> >the affinity really means.
>
> Not if the application is designed to handle it. How would hotplug
> scripts make this any different, anyway?

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.

Solving it from hotplug scripts means the task's affinity is not
automatically violated. It means the decision to violate the affinity was
made in user-space, probably by the admin, who CAN know what the affinity
means.

> Rusty thought you just wouldn't send it unless the process was handling
> it.

I remembered that after I sent it, sorry. :)