On Fri, 23 Jun 2006, Nick Piggin wrote:
> > >Hugh Dickins wrote:
> > >
> > > >I'd expect tasks bound to the unplugged cpu simply not to be run
> > > >until "that" cpu is plugged back in.
> >
> > I wasn't meaning "kill -9" for the swsusp case, but for the general
> > unplug cpu case. We have a number of homeless tasks, which the admin
> > might want to run again when "the" cpu is plugged back in; or might
> > want to kill off without having to plug a cpu back in.
>
> Possible maybe... I presumed that would lead to a nightmare of
> resource deadlocks (think mutexes).
Yes, that's what I've naively overlooked - thanks.
But _maybe_ there's still a case for allowing such tasks to run
_in_kernel_ on a wrong cpu, to release resources, and to be killed.
Hugh
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
