From: Matthew Wilcox <willy@infradead.org>
To: Hyeonggon Yoo <42.hyeyoo@gmail.com>
Cc: Christoph Lameter <cl@gentwo.de>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>
Subject: Re: Do we really need SLOB nowdays?
Date: Thu, 28 Oct 2021 13:08:02 +0100 [thread overview]
Message-ID: <YXqSoo+b9RTclW/2@casper.infradead.org> (raw)
In-Reply-To: <20211028100414.GA2928@kvm.asia-northeast3-a.c.our-ratio-313919.internal>
On Thu, Oct 28, 2021 at 10:04:14AM +0000, Hyeonggon Yoo wrote:
> On Mon, Oct 25, 2021 at 10:17:08AM +0200, Christoph Lameter wrote:
> > On Mon, 18 Oct 2021, Hyeonggon Yoo wrote:
> >
> > > > Better for what use case? SLOB is for machines with 1-16MB of RAM.
> > > >
> > >
> > > 1~16M is smaller than I thought. Hmm... I'm going to see how it works on
> > > tiny configuration. Thank you Matthew!
> >
> > Is there any reference where we can see such a configuration? Sure it does
> > not work with SLUB too?
>
> I thought why Matthew said "SLOB is for machines with 1-16MB of RAM"
> is because if memory is so low, then it is sensitive to memory usage.
>
> (But I still have doubt if we can run linux on machines like that.)
I sent you a series of articles about making Linux run in 1MB.
next prev parent reply other threads:[~2021-10-28 12:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 4:28 [RFC] More deterministic SLOB for real time embedded systems Hyeonggon Yoo
2021-10-17 13:36 ` segregated list + slab merging is much better than original SLOB Hyeonggon Yoo
2021-10-17 13:57 ` Do we really need SLOB nowdays? Hyeonggon Yoo
2021-10-17 14:39 ` Matthew Wilcox
2021-10-18 9:45 ` Hyeonggon Yoo
2021-10-25 8:17 ` Christoph Lameter
2021-10-28 10:04 ` Hyeonggon Yoo
2021-10-28 12:08 ` Matthew Wilcox [this message]
2021-10-30 6:12 ` Hyeonggon Yoo
[not found] ` <20211210110835.GA632811@odroid>
2021-12-10 12:06 ` Christoph Lameter
2021-12-14 17:24 ` Vlastimil Babka
[not found] ` <20211215062904.GA1150813@odroid>
2021-12-15 10:10 ` Vlastimil Babka
2021-12-15 15:23 ` Christoph Lameter
2022-02-18 10:13 ` Hyeonggon Yoo
2022-02-18 10:37 ` Hyeonggon Yoo
2022-02-18 16:10 ` David Laight
2022-02-19 11:59 ` Hyeonggon Yoo
2021-10-25 8:15 ` Christoph Lameter
2021-10-25 8:14 ` [RFC] More deterministic SLOB for real time embedded systems Christoph Lameter
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=YXqSoo+b9RTclW/2@casper.infradead.org \
--to=willy@infradead.org \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.de \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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