Messages in this thread | | | Date | Sat, 20 Feb 1999 12:46:24 -0500 (EST) | From | Gregory Maxwell <> | Subject | Re: Locking a process or thread onto a specific CPU |
| |
On Fri, 19 Feb 1999, Alexander S A Kjeldaas wrote:
> In order to kill it, you have to find it :-). And you won't with ps. > There's a race between ps and the process which the process almost always > wins. So it's hidden. The way you notice this kind of process is that the > load is 1, and top shows no processes using cpu. Then you know something > fishy is going on. You disable some CPUs, schedule your shell as > real-time, and only _then_ can you do a ps to find the offending user.
I think a more elegant solution would be a quick modification to the kernel that let it 'detect' fast forkers and slow their forks down by rescheduling.
Perhaps a ulimit --forks-per-second would be nice.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |