On Fri, 16 Jun 2006 12:36:50 +0200
Andi Kleen <[email protected]> wrote:
> > Assume there are some multi-threaded tasks with SCHED_FIFO.
> > If they uses some kind of synchronization in user land and task is migrated to
> > other cpus, it will cause dead-lock.
>
> If its CPU fails much worse things than that will happen.
>
> One way might be to break affinity of all processes in the system on hot unplug
> - then your deadlock would be avoided - but it might be a bit radical.
>
Hmm, ok. I undestand your point.
In "cpu is broken, so we have to remove it" case, my patch is harmful.
But (unpredictable) forced migration will cause something bad to user regardless
of scheduling type.
Should we send signal (kill or stop) to tasks whose cpus_allowed only contains
removed cpu rather than simple migration ?
(if this was discussed in past, I'm sorry)
-Kame
-
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]
