[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d6c57862-1593-44ff-a192-7af308cac94b@linux.intel.com>
Date: Wed, 13 Nov 2024 15:58:25 +0100
From: Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>
To: Tejun Heo <tj@...nel.org>, Maxime Ripard <mripard@...nel.org>
Cc: Johannes Weiner <hannes@...xchg.org>, intel-xe@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
Zefan Li <lizefan.x@...edance.com>, Andrew Morton
<akpm@...ux-foundation.org>, Friedrich Vock <friedrich.vock@....de>,
cgroups@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 0/7] kernel/cgroups: Add "dev" memory accounting cgroup.
Hey,
Den 2024-11-06 kl. 19:20, skrev Tejun Heo:
> On Wed, Nov 06, 2024 at 11:31:49AM +0100, Maxime Ripard wrote:
> ...
>>> How about dmem for this one, and dpu for the other one. For device
>>> memory and device processing unit, respectively.
>>
>> dmem sounds great to me, does everyone agree?
>
> Sounds good to me.
>
> Thanks.
>
Thanks for all feedback and discussion. I checked mostly on patchwork so
I missed the discussion here. Fortunately it's only been about naming. :)
I'm thinking of adding a 'high' knob as well, that will work similarly
to high in normal mem controller. (so not proportionally calculated like
'max', but (usage + allocated) < max = ok.
Recursively of course.
Cheers,
~Maarten
Powered by blists - more mailing lists