Hi 28.05.2015, 11:54, "Dimitri John Ledkov" <dimitri.j.ledkov@xxxxxxxxx>: > What you are saying is that we have inefficient notification mechanism > that hammers everyone's boot time significantly, and no current path > to resolve it. What can I do get us efficient cgroup release > notifications soon? > This patch-set is a no-op if one doesn't subscribe from the userspace > and has no other side effects that I can trivially see and is very > similar in-spirit to other notifications that proc-connector > generates. E.g. /proc/pid/comm is exposed as a file, yet there is proc > connector notification as well about comm name changes. Maybe Evgeniy > can chip in, if such a notification would be beneficial to > proc-connector. I understand your need in a new notifications related to cgroups, although I would rather put it into separate module than proc connector - I'm pretty sure there will be quite alot of extensions in this module in the future. But if you do want to extend proc connector module, I'm ok with it, but it should go via its maintainer. -- 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
