From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: linux-mm@kvack.org
Cc: 42.hyeyoo@gmail.com, Christoph Lameter <cl@linux.com>,
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>,
linux-kernel@vger.kernel.org
Subject: [QUESTION] is SLAB considered legacy and deprecated?
Date: Mon, 27 Sep 2021 09:03:47 +0000 [thread overview]
Message-ID: <20210927090347.GA2533@linux.asia-northeast3-a.c.our-ratio-313919.internal> (raw)
Hello there,
I've been working on adding 'lockless cache' on sl[au]b for a while.
But what it actually does is actually adding 'queuing' on slub.
So there is a fundamental question coming into my mind:
'is SLAB considered legacy and deprecated?'
It seems there are little development on SLAB and people think that
SLAB is legacy and deprecated, so CONFIG_SLUB is used by default.
But I think both has pros and cons for their own:
SLAB: more temporal locality (cache friendly)
but high usage of memory, and less spatial locality (TLB misses) than SLUB.
SLUB: less temporal locality (less cache friendly) than SLAB
but more spatial locality (TLB hit), and low usage of memory
and good debugging feature.
Why do people say SLAB is deprecated/legacy?
Thanks,
Hyeonggon
next reply other threads:[~2021-09-27 9:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 9:03 Hyeonggon Yoo [this message]
2021-09-27 17:03 ` Vlastimil Babka
2021-09-28 11:12 ` Hyeonggon Yoo
2021-09-29 10:50 ` Hyeonggon Yoo
2021-10-01 14:07 ` Vlastimil Babka
2021-10-03 5:59 ` Hyeonggon Yoo
2021-10-04 1:25 ` David Rientjes
2021-10-04 6:01 ` Hyeonggon Yoo
2021-10-04 11:39 ` Vlastimil Babka
2021-10-05 13:31 ` Hyeonggon Yoo
2021-10-04 11:34 ` Vlastimil Babka
2021-10-04 14:22 ` Hyeonggon Yoo
2021-10-01 0:39 ` Queueing is outside of SLUB nowdays Hyeonggon Yoo
2021-10-04 14:56 ` Christoph Lameter
2021-10-05 8:19 ` Vlastimil Babka
2021-10-05 14:16 ` Hyeonggon Yoo
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=20210927090347.GA2533@linux.asia-northeast3-a.c.our-ratio-313919.internal \
--to=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--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