linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: gouhao@uniontech.com
To: 42.hyeyoo@gmail.com
Cc: akpm@linux-foundation.org, cl@linux.com, gouhao@uniontech.com,
	gouhaojake@163.com, iamjoonsoo.kim@lge.com,
	keescook@chromium.org, linux-hardening@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org, mingo@elte.hu,
	penberg@kernel.org, rientjes@google.com,
	roman.gushchin@linux.dev, vbabka@suse.cz
Subject: Re: [PATCH] mm/slab: remove unused slab_early_init
Date: Sun, 18 Dec 2022 20:12:04 +0800	[thread overview]
Message-ID: <20221218121204.27720-1-gouhao@uniontech.com> (raw)
In-Reply-To: <Y551tFBVcYxPlFlH@hyeyoo>

Thanks for your review, i will fix it in next version patch. :)


Thanks,
Gou Hao
> 
> > 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>
> > ---
> >  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;
> > -- 
> > 2.20.1
> 
> Nice cleanup, thanks!
> 
> Acked-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>


  reply	other threads:[~2022-12-18 12:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-17 11:30 gouhao
2022-12-18  2:06 ` Hyeonggon Yoo
2022-12-18 12:12   ` gouhao [this message]
2022-12-18 12:21   ` gouhao

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=20221218121204.27720-1-gouhao@uniontech.com \
    --to=gouhao@uniontech.com \
    --cc=42.hyeyoo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=gouhaojake@163.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 \
    --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