On Fri, Nov 29, 2019 at 01:00:36AM -0500, Kenny Ho wrote:
> On Tue, Oct 1, 2019 at 10:31 AM Michal Koutný <mkoutny@xxxxxxxx> wrote:
> > On Thu, Aug 29, 2019 at 02:05:19AM -0400, Kenny Ho <Kenny.Ho@xxxxxxx> wrote:
> > > +struct cgroup_subsys drm_cgrp_subsys = {
> > > + .css_alloc = drmcg_css_alloc,
> > > + .css_free = drmcg_css_free,
> > > + .early_init = false,
> > > + .legacy_cftypes = files,
> > Do you really want to expose the DRM controller on v1 hierarchies (where
> > threads of one process can be in different cgroups, or children cgroups
> > compete with their parents)?
>
> (Sorry for the delay, I have been distracted by something else.)
> Yes, I am hoping to make the functionality as widely available as
> possible since the ecosystem is still transitioning to v2. Do you see
> inherent problem with this approach?
Integrating with memcg could be more challenging on cgroup1. That's
one of the reasons why e.g. cgroup-aware pagecache writeback is only
on cgroup2.
--
tejun
