3 ms·
Well, that's why I said that in the long term this might be solved. There is nothing as good right now, but in principle it could exist. Secondly, I doubt that
by IgorPartola 12y ago
Well, that's why I said that in the long term this might be solved. There is nothing as good right now, but in principle it could exist.
Secondly, I doubt that a process manager with support for cgroups would need to run on microcontrollers. At least up to this point, I have not seen many microcontrollers running Linux containers.
Lastly, a hybrid solution could be good: process manager identifies what processes to kill and in what order, oomkiller does the killing.
- npsimons 12y agoMy point about running on microcontrollers is that the Linux kernel (and oom-killer in particular) has been tested on more use cases than most developers usually consider. This testing/usage has revealed mistaken design decisions and bugs. Very few process managers created from scratch will have been tested on nearly as many use cases and will naturally not be as robust. I do agree with you about the hybrid solution, with a twist: since the oom-killer has been so widely tested, I would think that if someone needed different performance parameters, it might behoove them to start with the oom-killer and tune it, modifying the source if necessary, instead of re-inventing the wheel from scratch.