Hi, I read a lot about the new cgroup concept of the kernel/systemd. I understand the logic behind it and why systemd wants to be the MCP of it. But I miss information how threads are handled.
Example: Due to performance reasons we arrange components with various profiles into one executable. Assume a splash-animation on startup, audio-management, CAN, key input etc. Some of them should be protected by a realtime cgroup - others not. Right now we are able to put the whole unit/process into one cgroup with systemd mechanisms (I like the slice concept :)) Named threads can be handled by extra tooling, e.g. invoked via ExecStartPost, managing the threads/cgroups directly Problems will arise if manual management is impossible in future implementations. Is there a systemd concept if and/or how threads living inside of processes can be assigned to separate cgroups? Best regards Robert PS: resources I used: http://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/ http://lists.freedesktop.org/archives/systemd-devel/2013-June/011521.html ROBERT ALLMEROTH Harman Automotive Division Becker-Göring-Straße 16 76307 Karlsbad Phone: +49 (0) 7248-71-1156 Fax: +49 (0) 7248-71-2156 Email: [email protected] Web: www.harman.com _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
