linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: remove unneeded __meminit annotation
Date: Tue, 8 Aug 2023 04:16:57 +0100	[thread overview]
Message-ID: <ZNGzqRYzC8lbLG9s@casper.infradead.org> (raw)
In-Reply-To: <308f326d-c7ae-be49-22af-189a81a89aa2@huawei.com>

On Tue, Aug 08, 2023 at 11:08:36AM +0800, Miaohe Lin wrote:
> On 2023/8/8 10:31, Matthew Wilcox wrote:
> > On Tue, Aug 08, 2023 at 09:58:31AM +0800, Miaohe Lin wrote:
> >> kswapd_stop() and kcompactd_stop() are only called when MEMORY_HOTREMOVE
> >> is enabled. So wrap them under CONFIG_MEMORY_HOTREMOVE and further remove
> >> __meminit annotation. No functional change intended.
> > 
> > I don't understand why this is an improvement.  If CONFIG_MEMORY_HOTREMOVE
> > is disabled, the linker drops this section (... right?)  If it's enabled,
> 
> When CONFIG_MEMORY_HOTREMOVE is disabled, without this patch:
> 
> size mm/compaction.o
>    text	   data	    bss	    dec	    hex	filename
>  103164	  30873	      0	 134037	  20b95	mm/compaction.o
> 
> size mm/vmscan.o
>    text	   data	    bss	    dec	    hex	filename
>  158775	  49612	     64	 208451	  32e43	mm/vmscan.o
> 
> while with this patch:
> 
> size mm/compaction.o
>    text	   data	    bss	    dec	    hex	filename
>  102915	  30865	      0	 133780	  20a94	mm/compaction.o
> 
> size mm/vmscan.o
>    text	   data	    bss	    dec	    hex	filename
>  158534	  49604	     64	 208202	  32d4a	mm/vmscan.o
> 
> We can reduce each .o by ~250 bytes.

But this is before the linker step!  That will be where the meminit
sections get dropped.  Assuming they are; I haven't verified.  You need
to compare before/after of the vmlinux, not the individual .o files.



  reply	other threads:[~2023-08-08  3:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  1:58 Miaohe Lin
2023-08-08  2:31 ` Matthew Wilcox
2023-08-08  3:08   ` Miaohe Lin
2023-08-08  3:16     ` Matthew Wilcox [this message]
2023-08-08  3:26       ` Matthew Wilcox
2023-08-08  6:10         ` Miaohe Lin

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=ZNGzqRYzC8lbLG9s@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    /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