From: Vlastimil Babka <vbabka@suse.cz>
To: gouhao@uniontech.com, cl@linux.com, penberg@kernel.org,
rientjes@google.com, iamjoonsoo.kim@lge.com,
akpm@linux-foundation.org, roman.gushchin@linux.dev,
42.hyeyoo@gmail.com, keescook@chromium.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org, mingo@elte.hu
Subject: Re: [PATCH V2] mm/slab: remove unused slab_early_init
Date: Mon, 2 Jan 2023 09:39:28 +0100 [thread overview]
Message-ID: <0f330796-480e-0b78-c2f4-006eac38d7df@suse.cz> (raw)
In-Reply-To: <20221218123127.23810-1-gouhao@uniontech.com>
On 12/18/22 13:31, gouhao@uniontech.com wrote:
> From: Gou Hao <gouhao@uniontech.com>
>
> 'slab_early_init' was introduced by 'commit e0a42726794f
> ("[PATCH] mm/slab.c: fix early init assumption")', this
> flag was used to prevent off-slab caches being created
> so early during bootup.
>
> The only user of 'slab_early_init' was removed in 'commit
> 3217fd9bdf00 ("mm/slab: make criteria for off slab
> determination robust and simple")'.
>
> Signed-off-by: Gou Hao <gouhao@uniontech.com>
> Acked-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>
Thanks, added to slab/for-6.3/cleanups
> ---
> mm/slab.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/mm/slab.c b/mm/slab.c
> index 7a269db050ee..ede1f29fd81c 100644
> --- a/mm/slab.c
> +++ b/mm/slab.c
> @@ -220,7 +220,6 @@ static inline void fixup_objfreelist_debug(struct kmem_cache *cachep,
> static inline void fixup_slab_list(struct kmem_cache *cachep,
> struct kmem_cache_node *n, struct slab *slab,
> void **list);
> -static int slab_early_init = 1;
>
> #define INDEX_NODE kmalloc_index(sizeof(struct kmem_cache_node))
>
> @@ -1249,8 +1248,6 @@ void __init kmem_cache_init(void)
> slab_state = PARTIAL_NODE;
> setup_kmalloc_cache_index_table();
>
> - slab_early_init = 0;
> -
> /* 5) Replace the bootstrap kmem_cache_node */
> {
> int nid;
prev parent reply other threads:[~2023-01-02 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 12:31 gouhao
2022-12-28 1:46 ` David Rientjes
2023-01-02 8:39 ` Vlastimil Babka [this message]
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=0f330796-480e-0b78-c2f4-006eac38d7df@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=gouhao@uniontech.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
/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