From: kernel test robot <lkp@intel.com>
To: Sultan Alsawaf <sultan@kerneltoast.com>,
Jan Alexander Steffens (heftig) <heftig@archlinux.org>
Cc: oe-kbuild-all@lists.linux.dev, lkp@intel.com,
Josh Triplett <josh@joshtriplett.org>
Subject: [lkp] [+139 bytes kernel size regression] [i386-tinyconfig] [bf45053c96] ZEN: mm: Don't hog the CPU and zone lock in rmqueue_bulk()
Date: Tue, 29 Aug 2023 13:46:35 +0800 [thread overview]
Message-ID: <20230829054635.LaFn7%lkp@intel.com> (raw)
FYI, we noticed a +139 bytes kernel size regression due to commit:
commit: bf45053c965e9b8a0b6225c5d378493b5aaf1336 (ZEN: mm: Don't hog the CPU and zone lock in rmqueue_bulk())
https://github.com/zen-kernel/zen-kernel 6.5/zen-sauce
Details as below (size data is obtained by `nm --size-sort vmlinux`):
42ed39f2: ZEN: INTERACTIVE: Document PDS/BMQ configuration
bf45053c: ZEN: mm: Don't hog the CPU and zone lock in rmqueue_bulk()
+-------------------+----------+----------+-------+
| symbol | 42ed39f2 | bf45053c | delta |
+-------------------+----------+----------+-------+
| bzImage | 516656 | 516848 | 192 |
| nm.t.rmqueue_bulk | 353 | 492 | 139 |
+-------------------+----------+----------+-------+
Thanks
reply other threads:[~2023-08-29 5:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230829054635.LaFn7%lkp@intel.com \
--to=lkp@intel.com \
--cc=heftig@archlinux.org \
--cc=josh@joshtriplett.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sultan@kerneltoast.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.