[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.22.394.2110250957040.2528@gentwo.de>
Date: Mon, 25 Oct 2021 09:58:54 +0200 (CEST)
From: Christoph Lameter <cl@...two.de>
To: Hyeonggon Yoo <42.hyeyoo@...il.com>
cc: Vlastimil Babka <vbabka@...e.cz>, linux-kernel@...r.kernel.org,
Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
Matthew Wilcox <willy@...radead.org>,
Dave Taht <dave.taht@...il.com>
Subject: Re: [RFC PATCH] mm, slob: Rewrite SLOB using segregated free list
On Thu, 21 Oct 2021, Hyeonggon Yoo wrote:
> But on the contrary, I wonder when SLOB is useful than SLUB.
> is it for really tiny linux systems that has under 1M of RAM?
> But can linux be that small?
SLOB I think is mainly a nice intro into how slab allocators work. It is a
simple architecture and the code is to read and therefore easily
understood. I heard of some use cases from others but I have only ever
been able to run a kernel boot in KVM with SLOB.
Powered by blists - more mailing lists