linux-kernel - Re: [RFC 2/3] mm: introduce GCMA

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: <Z9z1w2vHfJrwSgWW@infradead.org>
Date: Thu, 20 Mar 2025 22:14:43 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: akpm@...ux-foundation.org, willy@...radead.org, david@...hat.com,
	vbabka@...e.cz, lorenzo.stoakes@...cle.com, liam.howlett@...cle.com,
	alexandru.elisei@....com, peterx@...hat.com, hannes@...xchg.org,
	mhocko@...nel.org, m.szyprowski@...sung.com, iamjoonsoo.kim@....com,
	mina86@...a86.com, axboe@...nel.dk, viro@...iv.linux.org.uk,
	brauner@...nel.org, hch@...radead.org, jack@...e.cz,
	hbathini@...ux.ibm.com, sourabhjain@...ux.ibm.com,
	ritesh.list@...il.com, aneesh.kumar@...nel.org, bhelgaas@...gle.com,
	sj@...nel.org, fvdl@...gle.com, ziy@...dia.com, yuzhao@...gle.com,
	minchan@...nel.org, linux-mm@...ck.org,
	linuxppc-dev@...ts.ozlabs.org, linux-block@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, iommu@...ts.linux.dev,
	linux-kernel@...r.kernel.org, Minchan Kim <minchan@...gle.com>
Subject: Re: [RFC 2/3] mm: introduce GCMA

On Thu, Mar 20, 2025 at 10:39:30AM -0700, Suren Baghdasaryan wrote:
> From: Minchan Kim <minchan@...gle.com>
> 
> This patch introduces GCMA (Guaranteed Contiguous Memory Allocator)
> cleacache backend which reserves some amount of memory at the boot
> and then donates it to store clean file-backed pages in the cleancache.
> GCMA aims to guarantee contiguous memory allocation success as well as
> low and deterministic allocation latency.
> 
> Notes:
> Originally, the idea was posted by SeongJae Park and Minchan Kim [1].
> Later Minchan reworked it to be used in Android as a reference for
> Android vendors to use [2].

That is not a very good summay.  It needs to explain how you ensure
that the pages do stay clean forever.