linux-kernel - Re: Requirements to merge new heaps in the kernel

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: <35deac48-4220-4889-833d-1b57b417e968@gmx.de>
Date: Wed, 30 Oct 2024 12:16:22 +0100
From: metux <metux@....de>
To: Maxime Ripard <mripard@...hat.com>, Sumit Semwal <sumit.semwal@...aro.org>
Cc: Benjamin Gaignard <benjamin.gaignard@...labora.com>,
 Brian Starkey <Brian.Starkey@....com>, John Stultz <jstultz@...gle.com>,
 "T.J. Mercier" <tjmercier@...gle.com>,
 Christian König <christian.koenig@....com>,
 linux-media@...r.kernel.org, dri-devel@...ts.freedesktop.org,
 linaro-mm-sig@...ts.linaro.org, linux-kernel@...r.kernel.org
Subject: Re: Requirements to merge new heaps in the kernel

On 22.10.24 10:38, Maxime Ripard wrote:

Hi,

> I'm still interested in merging a carve-out driver[1], since it seems to be
> in every vendor BSP and got asked again last week.
>
> I remember from our discussion that for new heap types to be merged, we
> needed a kernel use-case. Looking back, I'm not entirely sure how one
> can provide that given that heaps are essentially facilities for
> user-space.

For those who didn't follow your work, could you please give a short
intro what's that all about ?

If I understand you correctly, you'd like the infrastructure of
kmalloc() et al for things / memory regions that aren't the usual heap,
right ?

What's the practical use case ? GPU memory ? Shared memory between
nodes in a multi-CPU / cluster machine ?

Is it related to NUMA ?

thx
--mtx