Well, it really depends on the application. *If* it spends a lot of time in the kernel, or worse gets locked in it, then the whole machine will come to a halt.
From the description it seems like the kernel is shared (no 'one kernel for one virtual host') so extensive locking performed on behalf on one application *will* influence others. Even if you have lots of extensive computing power.
Or just imagine - 99% of CPU hogged by an application you cannot kill. Or is there some form of 'master' context that can influence all others?
Slashdot Mirror
Well, it really depends on the application. *If* it spends a lot of time in the kernel, or worse gets locked in it, then the whole machine will come to a halt.
From the description it seems like the kernel is shared (no 'one kernel for one virtual host') so extensive locking performed on behalf on one application *will* influence others. Even if you have lots of extensive computing power.
Or just imagine - 99% of CPU hogged by an application you cannot kill. Or is there some form of 'master' context that can influence all others?
Well, isn't it a very old story? I remember seeing it on /. quite a while ago.