From: kernel test robot <lkp@intel.com>
To: Lorenzo Stoakes <lstoakes@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, lkp@intel.com,
Josh Triplett <josh@joshtriplett.org>
Subject: [lkp] [+328 bytes kernel size regression] [i386-tinyconfig] [1b7c843021] mm: vmalloc: use rwsem, mutex for vmap_area_lock and vmap_block->lock
Date: Sun, 19 Mar 2023 16:29:05 +0800 [thread overview]
Message-ID: <ZBbH0eLnZ7Y285ae@a245b58858a4> (raw)
In-Reply-To: <6c7f1ac0aeb55faaa46a09108d3999e4595870d9.1679209395.git.lstoakes@gmail.com>
FYI, we noticed a +328 bytes kernel size regression due to commit:
commit: 1b7c843021466759acc93c26bf63bfdabf51398c (mm: vmalloc: use rwsem, mutex for vmap_area_lock and vmap_block->lock)
url: https://github.com/intel-lab-lkp/linux/commits/Lorenzo-Stoakes/fs-proc-kcore-Avoid-bounce-buffer-for-ktext-data/20230319-151114
patch link: https://lore.kernel.org/all/6c7f1ac0aeb55faaa46a09108d3999e4595870d9.1679209395.git.lstoakes@gmail.com/
patch subject: [PATCH v2 2/4] mm: vmalloc: use rwsem, mutex for vmap_area_lock and vmap_block->lock
Details as below (size data is obtained by `nm --size-sort vmlinux`):
fcb76393: fs/proc/kcore: Avoid bounce buffer for ktext data
1b7c8430: mm: vmalloc: use rwsem, mutex for vmap_area_lock and vmap_block->lock
+----------------------------------+----------+----------+-------+
| symbol | fcb76393 | 1b7c8430 | delta |
+----------------------------------+----------+----------+-------+
| bzImage | 501536 | 501760 | 224 |
| nm.t.vb_free | 178 | 210 | 32 |
| nm.T.find_vmap_area | 6 | 36 | 30 |
| nm.t.purge_fragmented_blocks | 276 | 306 | 30 |
| nm.T.vread | 345 | 373 | 28 |
| nm.t.vb_alloc | 196 | 222 | 26 |
| nm.t.find_unlink_vmap_area | 49 | 73 | 24 |
| nm.t.alloc_vmap_area | 1264 | 1288 | 24 |
| nm.t.free_vmap_block | 117 | 140 | 23 |
| nm.t.__get_vm_area_node | 218 | 240 | 22 |
| nm.t._vm_unmap_aliases | 148 | 168 | 20 |
| nm.t.free_vmap_area | 676 | 696 | 20 |
| nm.t.new_vmap_block | 339 | 357 | 18 |
| nm.d.vmap_area_lock | 0 | 16 | 16 |
| nm.t.vmap_ram_vread | 259 | 272 | 13 |
| nm.T.remap_vmalloc_range_partial | 164 | 166 | 2 |
+----------------------------------+----------+----------+-------+
Thanks
next prev parent reply other threads:[~2023-03-19 8:30 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 7:09 [PATCH v2 0/4] convert read_kcore(), vread() to use iterators Lorenzo Stoakes
2023-03-19 7:09 ` [PATCH v2 1/4] fs/proc/kcore: Avoid bounce buffer for ktext data Lorenzo Stoakes
2023-03-20 9:58 ` David Hildenbrand
2023-03-19 7:09 ` [PATCH v2 2/4] mm: vmalloc: use rwsem, mutex for vmap_area_lock and vmap_block->lock Lorenzo Stoakes
2023-03-19 8:29 ` kernel test robot [this message]
2023-03-19 20:10 ` Andrew Morton
2023-03-19 20:29 ` Lorenzo Stoakes
2023-03-19 20:47 ` Matthew Wilcox
2023-03-19 21:16 ` Lorenzo Stoakes
2023-03-20 8:40 ` Lorenzo Stoakes
2023-03-20 7:54 ` Uladzislau Rezki
2023-03-20 8:25 ` Lorenzo Stoakes
2023-03-20 8:32 ` Uladzislau Rezki
2023-03-20 8:35 ` Lorenzo Stoakes
2023-03-20 11:20 ` Uladzislau Rezki
2023-03-21 1:09 ` Dave Chinner
2023-03-21 5:23 ` Uladzislau Rezki
2023-03-21 7:45 ` Lorenzo Stoakes
2023-03-21 8:54 ` Uladzislau Rezki
2023-03-21 10:05 ` Dave Chinner
2023-03-21 10:24 ` Uladzislau Rezki
2023-03-22 13:18 ` Uladzislau Rezki
2023-03-22 17:47 ` Matthew Wilcox
2023-03-22 18:01 ` Uladzislau Rezki
2023-03-22 19:15 ` Uladzislau Rezki
2023-03-23 12:47 ` Uladzislau Rezki
2023-03-24 5:25 ` Dave Chinner
2023-03-24 5:31 ` Matthew Wilcox
2023-03-27 0:38 ` Dave Chinner
2023-03-27 17:22 ` Uladzislau Rezki
2023-03-28 2:53 ` Dave Chinner
2023-03-28 12:40 ` Uladzislau Rezki
2023-03-19 7:09 ` [PATCH v2 3/4] fs/proc/kcore: convert read_kcore() to read_kcore_iter() Lorenzo Stoakes
2023-03-19 7:09 ` [PATCH v2 4/4] mm: vmalloc: convert vread() to vread_iter() Lorenzo Stoakes
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=ZBbH0eLnZ7Y285ae@a245b58858a4 \
--to=lkp@intel.com \
--cc=josh@joshtriplett.org \
--cc=lstoakes@gmail.com \
--cc=oe-kbuild-all@lists.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 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.