linux-kernel - Re: [PATCH] mm: remove all the slab allocators

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] [day] [month] [year] [list]

Message-ID: <ZClhKouKa5e6/jha@casper.infradead.org>
Date:   Sun, 2 Apr 2023 12:04:10 +0100
From:   Matthew Wilcox <willy@...radead.org>
To:     郭辉 <guohui@...ontech.com>
Cc:     Vlastimil Babka <vbabka@...e.cz>, linux-mm@...ck.org,
        linux-kernel@...r.kernel.org, patches@...ts.linux.dev
Subject: Re: [PATCH] mm: remove all the slab allocators

On Sun, Apr 02, 2023 at 05:09:14PM +0800, 郭辉 wrote:
> On 4/1/23 5:46 PM, Vlastimil Babka wrote:
> > As the SLOB removal is on track and the SLAB removal is planned, I have
> > realized - why should we stop there and not remove also SLUB? What's a
> > slab allocator good for in 2023? The RAM sizes are getting larger and
> > the modules cheaper [1]. The object constructor trick was perhaps
> > interesting in 1994, but not with contemporary CPUs. So all the slab
> > allocator does today is just adding an unnecessary layer of complexity
> > over the page allocator.
> 
> The slab allocator is very core and very important to the Linux kernel.
> After the patch is merged into the mainline, it will have a very profound
> impact on the development of the Linux kernel.

https://en.wikipedia.org/wiki/April_Fools%27_Day