Messages in this thread | | | Date | Mon, 06 Feb 2006 23:36:44 +0300 | From | Kirill Korotaev <> | Subject | Re: RFC [patch 13/34] PID Virtualization Define new task_pid api |
| |
>>There are two issues here. >>1) Monitoring. (ps, top etc) >>2) Control (kill). >> >>For monitoring you might need to patch ps/top a little but it is doable without >>2 pids. >> >>For kill it is extremely rude to kill processes inside of a nested pid space. >>There are other solutions to the problem.
> Can you elaborate? If I have 10 containers with 1000 processes each, > it would be nice to be able to run top then kill 40 top cpu hogs.... This is exactly the reason why we allow host system to see all the containers/VPSs/processes.
Otherwise monitoring tools should be fixed for it, which doesn't look good and top/ps/kill are not the only tools in the world. Without such functionality you can't understand whether you machine is underloaded or overloaded.
Kirill
- 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/
| |