On Fri, 2005-02-25 at 16:02 -0500, Chad N. Tindel wrote: > They're expensive and customers don't expect a single userspace thread to > tie up the other 63 CPUs no matter how buggy it is. It is intuitively obvious > that a buggy kernel can bring a system to its knees, but it is not intuitively > obvious that a buggy userspace app can do the same thing. It is more of a > supportability issue than anything, because you expect the other processors > to function properly so you can get in and live-debug the application when it > hits a bug that makes it CPU-bound. This is especially important if the box > is, say, in a remote jungle of China or something where you don't have access > to the console.
"Unix policy is to not stop root from doing stupid things because that would also stop him from doing clever things." - Andi Kleen "It's such a fine line between stupid and clever" - Derek Smalls Lee - 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/
