Hello, Matt. On Fri, Jan 19, 2018 at 05:51:38PM -0800, Matt Roper wrote: > Most DRM drivers will want to handle the CGROUP_SETPARAM ioctl by looking up a > driver-specific per-cgroup data structure (or allocating a new one) and > storing > the supplied parameter value into the data structure (possibly after doing > some > checking and sanitization on the provided value). Let's provide a helper > library for drivers that will take care of the details of storing per-cgroup > data structures in a hashtable and destroying those structures if/when the > cgroup itself is removed.
Would it be possible to make the core of this a built-in part of cgroup like cgroup-bpf does? My gut feeling is that that isn't gonna be much code anyway and likely to be cleaner to implement and use. Being a full-fledged controller comes with quite a bit of complexity in terms of sync rules and everything, and we may build a simpler modular infrastructure if usages like this proliferate but for now extending from the core seems the most straight forward. Thanks. -- tejun _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
