From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-mm@kvack.org, 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>,
linux-kernel@vger.kernel.org
Subject: Re: [QUESTION] is SLAB considered legacy and deprecated?
Date: Wed, 29 Sep 2021 10:50:56 +0000 [thread overview]
Message-ID: <20210929105056.GA2575@linux.asia-northeast3-a.c.our-ratio-313919.internal> (raw)
In-Reply-To: <20210928111231.GA2596@linux.asia-northeast3-a.c.our-ratio-313919.internal>
On Tue, Sep 28, 2021 at 11:12:36AM +0000, Hyeonggon Yoo wrote:
> SLAB uses much memory than slab,
not slab, slub.
> when there are *lots* of NUMA nodes.
> because kmem_cache_node exist per node and it keeps alien cache
> (used for caching freeing object from remote node),
> so it keeps MAX_NUMANODES ^ 2 of array_cache per slab.
not "per slab". it is per cache (kmem_cache).
it was my mistake. but that is still too much for
systems with high number of numa nodes.
batching freeing object from remote node is needed,
but slab uses too much memory for that.
for each node, it allocates alien cache for every other nodes.
so it's using MAX_NUMNODES ^ 2 alien_cache.
> that is why I said SLAB uses much memory than SLUB.
next prev parent reply other threads:[~2021-09-29 10:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 9:03 Hyeonggon Yoo
2021-09-27 17:03 ` Vlastimil Babka
2021-09-28 11:12 ` Hyeonggon Yoo
2021-09-29 10:50 ` Hyeonggon Yoo [this message]
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=20210929105056.GA2575@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