linux-kernel - Re: [PATCH v2 0/7] kernel/cgroups: Add "dmem" memory accounting cgroup.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <61b95c08-a3c2-4f92-b6e5-df77fd2491e2@lankhorst.se>
Date: Tue, 17 Dec 2024 21:17:24 +0100
From: Maarten Lankhorst <dev@...khorst.se>
To: Tejun Heo <tj@...nel.org>, Simona Vetter <simona.vetter@...ll.ch>,
 Dave Airlie <airlied@...il.com>
Cc: Maxime Ripard <mripard@...nel.org>, linux-kernel@...r.kernel.org,
 intel-xe@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
 Zefan Li <lizefan.x@...edance.com>, Johannes Weiner <hannes@...xchg.org>,
 Andrew Morton <akpm@...ux-foundation.org>,
 Friedrich Vock <friedrich.vock@....de>, cgroups@...r.kernel.org,
 linux-mm@...ck.org, Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>
Subject: Re: [PATCH v2 0/7] kernel/cgroups: Add "dmem" memory accounting
 cgroup.

Hey,

Den 2024-12-17 kl. 19:23, skrev Tejun Heo:
> Hello,
> 
> On Tue, Dec 17, 2024 at 06:37:22PM +0100, Maarten Lankhorst wrote:
>> Den 2024-12-17 kl. 18:11, skrev Tejun Heo:
>>> On Tue, Dec 17, 2024 at 03:28:50PM +0100, Maarten Lankhorst wrote:
>>>> Now that all patches look good, what is needed to merge the series? Without
>>>> patch 6/7 as it is a hack for testing.
>>>
>>> There were some questions raised about device naming. One thing we want to
>>> get right from the beginning is the basic interface.
>>>
>>> Thanks.
>>>
>> I believe it was solved. The conclusion appears to be that we go with how we
>> defined it in this series. drm/$pciid/$regionname. With the only regions
>> defined now being VRAM. Main memory will be a followup, but requires some
>> discussions on hwo to be prevent double accounting, and what to do with the
>> limited amount of mappable memory.
> 
> Provided Johannes is okay with the series, how do you want to route the
> series? If you want to route it through drm, that's fine by me and please
> feel free to add:
> 
>   Acked-by: Tejun Heo <tj@...nel.org>
> 
> Thanks.
> 

Thank you!

I've discussed this with the DRM maintainers. What was suggested is to 
create a topic branch, merge it to drm-misc whichwhere it will be picked 
up into drm.git during the next pull request. At the same time the topic 
branch can be also be merged into the cgroup tree if needed.

The drm-misc tree already handles dma-buf and fbdev core, think DMEM 
could fit in there too.

Cheers,
~Maarten