[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-cgroups
Subject:    Re: [PATCH RFC v4 02/16] cgroup: Introduce cgroup for drm subsystem
From:       Kenny Ho <y2kenny () gmail ! com>
Date:       2019-11-29 6:00:36
Message-ID: CAOWid-ewvs-c-z_WW+Cx=Jaf0p8ZAwkWCkq2E8Xkj+2HvfNjaA () mail ! gmail ! com
[Download RAW message or body]

On Tue, Oct 1, 2019 at 10:31 AM Michal Koutný <mkoutny@suse.com> wrote:
> On Thu, Aug 29, 2019 at 02:05:19AM -0400, Kenny Ho <Kenny.Ho@amd.com> 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?

Regards,
Kenny


>
> > +     .dfl_cftypes    = files,
> > +};
>
> Just asking,
> Michal
[prev in list] [next in list] [prev in thread] [next in thread]