From: kernel test robot <lkp@intel.com>
To: Doug Berger <opendmb@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, lkp@intel.com,
Josh Triplett <josh@joshtriplett.org>
Subject: [lkp] [+661 bytes kernel size regression] [i386-tinyconfig] [f9fbaaba68] mm/dmb: Introduce Designated Movable Blocks
Date: Sat, 11 Mar 2023 12:47:15 +0800 [thread overview]
Message-ID: <ZAwH0yRdrWjLNB69@ea1f349249c4> (raw)
In-Reply-To: <20230311003855.645684-8-opendmb@gmail.com>
FYI, we noticed a +661 bytes kernel size regression due to commit:
commit: f9fbaaba68da88b0ea457feacab434a3fc655153 (mm/dmb: Introduce Designated Movable Blocks)
url: https://github.com/intel-lab-lkp/linux/commits/Doug-Berger/lib-show_mem-c-display-MovableOnly/20230311-084243
base: https://git.kernel.org/cgit/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/all/20230311003855.645684-8-opendmb@gmail.com/
patch subject: [PATCH v4 7/9] mm/dmb: Introduce Designated Movable Blocks
Details as below (size data is obtained by `nm --size-sort vmlinux`):
3857ef0e: memblock: introduce MEMBLOCK_MOVABLE flag
f9fbaaba: mm/dmb: Introduce Designated Movable Blocks
+---------------------------------------+----------+----------+-------+
| symbol | 3857ef0e | f9fbaaba | delta |
+---------------------------------------+----------+----------+-------+
| bzImage | 501664 | 502176 | 512 |
| nm.t.calculate_node_totalpages | 0 | 352 | 352 |
| nm.t.zone_absent_pages_in_node | 0 | 334 | 334 |
| nm.T.dmb_reserve | 0 | 127 | 127 |
| nm.T.dmb_intersects | 0 | 81 | 81 |
| nm.T.dmb_init_region | 0 | 77 | 77 |
| nm.b.dmb_areas | 0 | 56 | 56 |
| nm.t.find_zone_movable_pfns_for_nodes | 546 | 592 | 46 |
| nm.T.memblock_free_all | 382 | 395 | 13 |
| nm.b.dmb_area_count | 0 | 4 | 4 |
| nm.d.max_dmb_pfn | 0 | 4 | 4 |
| nm.d.min_dmb_pfn | 0 | 4 | 4 |
| nm.T.absent_pages_in_range | 11 | 14 | 3 |
| nm.T.free_area_init | 1408 | 968 | -440 |
+---------------------------------------+----------+----------+-------+
Thanks
next prev parent reply other threads:[~2023-03-11 4:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 0:38 [PATCH v4 0/9] mm: introduce Designated Movable Blocks Doug Berger
2023-03-11 0:38 ` [PATCH v4 1/9] lib/show_mem.c: display MovableOnly Doug Berger
2023-03-11 0:38 ` [PATCH v4 2/9] mm/page_alloc: calculate node_spanned_pages from pfns Doug Berger
2023-03-11 0:38 ` [PATCH v4 3/9] mm/page_alloc: prevent creation of empty zones Doug Berger
2023-03-11 0:38 ` [PATCH v4 4/9] mm/page_alloc.c: allow oversized movablecore Doug Berger
2023-03-11 0:38 ` [PATCH v4 5/9] mm/page_alloc: introduce init_reserved_pageblock() Doug Berger
2023-03-11 0:38 ` [PATCH v4 6/9] memblock: introduce MEMBLOCK_MOVABLE flag Doug Berger
2023-03-11 0:38 ` [PATCH v4 7/9] mm/dmb: Introduce Designated Movable Blocks Doug Berger
2023-03-11 4:47 ` kernel test robot [this message]
2023-03-11 0:38 ` [PATCH v4 8/9] mm/page_alloc: make alloc_contig_pages DMB aware Doug Berger
2023-03-11 0:38 ` [PATCH v4 9/9] mm/page_alloc: allow base for movablecore Doug Berger
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=ZAwH0yRdrWjLNB69@ea1f349249c4 \
--to=lkp@intel.com \
--cc=josh@joshtriplett.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=opendmb@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.