Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Sun, 2 Apr 2023 12:04:10 +0100
From:   Matthew Wilcox <willy@infradead.org>
To:     =?utf-8?B?6YOt6L6J?= <guohui@uniontech.com>
Cc:     Vlastimil Babka <vbabka@suse.cz>, linux-mm@kvack.org,
        linux-kernel@vger.kernel.org, patches@lists.linux.dev
Subject: Re: [PATCH] mm: remove all the slab allocators
Message-ID: <ZClhKouKa5e6/jha@casper.infradead.org>
References: <20230401094658.11146-1-vbabka@suse.cz>
 <D9446192D1350A06+edeebc7d-b55d-571e-ef25-98ecb9d2662b@uniontech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <D9446192D1350A06+edeebc7d-b55d-571e-ef25-98ecb9d2662b@uniontech.com>
Precedence: bulk

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