![]() | |||||||||||
Messages in this thread |
On Sat, 17 Jun 2006 13:46:30 +1000 Nick Piggin <nickpiggin@yahoo.com.au> wrote: > > 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. > > Agreed. The kernel is just doing some basic fallback behaviour. If you > actually have a critical RT system, you probably need to have much more > sophisticated handling of CPU unplug anyway. So it doesn't make much > sense to complicate the kernel for this. > But it seems the kernel does what users doesn't want. threads which is tightly coupled to some cpu has some important meanings for the userk. If the apps are sophisticated as you say, cpus_allowed containes other cpus before hotplug. As SIGSTOP/KILL patch I posted, the apps shouldn't do unexpected work, I think. -Kame - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2006-06-17 07:14 [from the cache] ©2003-2008 | |||||||||||