Requirements to merge new heaps in the kernel

[Al Viro]

On Thu, Oct 31, 2024 at 05:45:23PM +0100, Maxime Ripard wrote:
> On Wed, Oct 30, 2024 at 12:16:22PM +0100, metux wrote:
> > On 22.10.24 10:38, Maxime Ripard wrote:
> > > 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 ?
> 
> No, not really. The discussion is about dma-buf heaps. They allow to
> allocate buffers suitable for DMA from userspace. It might or might not
> from the system memory, at the heap driver discretion.

I'm afraid you've misinterpreted that - our hexapedal friend had just
	* noticed that excessive crossposting can get it banned
	* got itself a new address
	* posted a solitary ping as the first test
	* followed that by testing the ability to cross-post (posting you'd
been replying to, contents on chatGPT level)
	* proceeded to use its shiny new address for more of the chorus
whinge exercise they'd been holding with several other similar fellows
(or sock puppets, for all I know).

Just ignore the wanker - it wasn't trying to get any information other
than "will the posting get through" anyway.