Re: [RFC PATCH v2 0/5] new cgroup controller for gpu/drm subsystem

2019-05-10 Thread Koenig, Christian
Am 10.05.19 um 17:07 schrieb Kenny Ho: > [CAUTION: External Email] > > On Fri, May 10, 2019 at 8:31 AM Christian König > wrote: >> I think it is a good approach to try to add a global limit first and >> when that's working go ahead with limiting device specific resources. > What are some of the

Re: [RFC PATCH v2 0/5] new cgroup controller for gpu/drm subsystem

2019-05-10 Thread Kenny Ho
On Fri, May 10, 2019 at 8:31 AM Christian König wrote: > > I think it is a good approach to try to add a global limit first and > when that's working go ahead with limiting device specific resources. What are some of the global drm resource limit/allocation that would be useful to implement? I

Re: [RFC PATCH v2 0/5] new cgroup controller for gpu/drm subsystem

2019-05-10 Thread Christian König
That looks better than I thought it would be. I think it is a good approach to try to add a global limit first and when that's working go ahead with limiting device specific resources. The only major issue I can see is on patch #4, see there for further details. Christian. Am 09.05.19 um

[RFC PATCH v2 0/5] new cgroup controller for gpu/drm subsystem

2019-05-09 Thread Kenny Ho
This is a follow up to the RFC I made last november to introduce a cgroup controller for the GPU/DRM subsystem [a]. The goal is to be able to provide resource management to GPU resources using things like container. The cover letter from v1 is copied below for reference. Usage examples: //