From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: 郭辉 <guohui@uniontech.com>, "Vlastimil Babka" <vbabka@suse.cz>,
Linux-MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
patches@lists.linux.dev
Subject: Re: [PATCH] mm: remove all the slab allocators
Date: Mon, 3 Apr 2023 05:51:42 +0200 [thread overview]
Message-ID: <CAPj211unsM2zM8Y-7iZ09jmKF135xZ6pSPzyzN2dkFvN=wUZFA@mail.gmail.com> (raw)
In-Reply-To: <ZClhKouKa5e6/jha@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]
On Sun, 2 Apr 2023, 13:04 Matthew Wilcox, <willy@infradead.org> wrote:
> 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
Wow!
The most interesting implication of this "patch" is that you noticed that
some people may actually need the link above to be able to distinguish
between foolishness and reality...
Thanks :-)
Fabio
[-- Attachment #2: Type: text/html, Size: 1881 bytes --]
next prev parent reply other threads:[~2023-04-03 3:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 9:46 Vlastimil Babka
2023-04-01 10:00 ` Lorenzo Stoakes
2023-04-01 10:25 ` Yosry Ahmed
2023-04-01 11:33 ` Petr Tesařík
2023-04-01 11:38 ` Vlastimil Babka
2023-04-01 15:15 ` Matthew Wilcox
2023-04-01 18:33 ` David Laight
2023-04-01 18:45 ` Christophe Leroy
2023-04-01 22:04 ` David Laight
2023-04-02 5:09 ` Jeff Xie
2023-04-02 9:09 ` 郭辉
2023-04-02 11:04 ` Matthew Wilcox
2023-04-03 3:51 ` Fabio M. De Francesco [this message]
2023-04-03 4:04 ` Fabio M. De Francesco
2023-04-03 4:13 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPj211unsM2zM8Y-7iZ09jmKF135xZ6pSPzyzN2dkFvN=wUZFA@mail.gmail.com' \
--to=fmdefrancesco@gmail.com \
--cc=guohui@uniontech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=patches@lists.linux.dev \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox