Hello, Krzysztof. On Tue, Mar 07, 2017 at 12:19:52PM +0100, Krzysztof Opasiak wrote: > So maybe let me clarify our use case so we can have some more discussion > about this. We are dealing with task of monitoring system services on an IoT > system. So this system needs to run as long as possible without reboot just > like server. In server world almost whole system state is being monitored by > services like nagios. They measure each parameter (like cpu, memory etc) > with some interval. Unfortunately we cannot use this it in an embedded > system due to power consumption. So, we don't add controllers for specific use case scenarios. The target actually has to be a fundamental resource which can't be isolated in a different way. The use case you're describing is more about working around shortcomings in userspace by implemneting a major kernel feature, when the said shortcomings can easily be controlled and mitigated from userspace - e.g. if running out of fds can't be handled reliably from the target application for some reason and the application may lock up from the condition, protect the base resources so that a monitoring process can always reliably run and let that take a corrective action when such condition is detected. This doesn't really seem to qualify as a dedicated kernel functionality. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
