[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9200b403-6376-96da-d84c-783a3371f73f@linux.intel.com>
Date: Tue, 25 Jul 2023 14:46:58 +0100
From: Tvrtko Ursulin <tvrtko.ursulin@...ux.intel.com>
To: Tejun Heo <tj@...nel.org>
Cc: Intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
Johannes Weiner <hannes@...xchg.org>,
Zefan Li <lizefan.x@...edance.com>,
Dave Airlie <airlied@...hat.com>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Rob Clark <robdclark@...omium.org>,
Stéphane Marchesin <marcheu@...omium.org>,
"T . J . Mercier" <tjmercier@...gle.com>, Kenny.Ho@....com,
Christian König <christian.koenig@....com>,
Brian Welty <brian.welty@...el.com>,
Tvrtko Ursulin <tvrtko.ursulin@...el.com>,
Michal Koutný <mkoutny@...e.com>
Subject: Re: [PATCH 12/17] cgroup/drm: Introduce weight based drm cgroup
control
On 21/07/2023 23:17, Tejun Heo wrote:
> On Wed, Jul 12, 2023 at 12:46:00PM +0100, Tvrtko Ursulin wrote:
>> +DRM scheduling soft limits
>> +~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Please don't say soft limits for this. It means something different for
> memcg, so it gets really confusing. Call it "weight based CPU time control"
> and maybe call the triggering points as thresholds.
Yes sorry, you said that before and I forgot to reword it all when
re-spinning. I have now marked it as TODO in my email client so
hopefully next time round I don't forget.
Regards,
Tvrtko
Powered by blists - more mailing lists