[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260115194450.GA3634291@ZenIV>
Date: Thu, 15 Jan 2026 19:44:50 +0000
From: Al Viro <viro@...iv.linux.org.uk>
To: "Christoph Lameter (Ampere)" <cl@...two.org>
Cc: linux-mm@...ck.org, Vlastimil Babka <vbabka@...e.cz>,
Harry Yoo <harry.yoo@...cle.com>, linux-fsdevel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
Mateusz Guzik <mguzik@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 00/15] kmem_cache instances with static storage
duration
On Thu, Jan 15, 2026 at 11:10:00AM -0800, Christoph Lameter (Ampere) wrote:
> Internal functions exist in the slab allocator that do what you want if
> the opaqueness requirement is dropped. F.e. for the creation of kmalloc
> caches we use do_kmem_cache_create():
Yes, I know. Do you really want to expose e.g. slab_caches and slab_mutex
to the rest of the kernel? Surgery needed to have __kmem_cache_create()
do everything is not large - see the mm/slab_common.c parts in the first
two commits in this series.
Powered by blists - more mailing lists