All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [lkp] [+618 bytes kernel size regression] [i386-tinyconfig] [0a27074469] rcu/tiny: support reclaim for head-less object
Date: Wed, 29 Apr 2020 14:01:51 +0800	[thread overview]
Message-ID: <20200429060150.GA43416@04cb3a94dea8> (raw)

[-- Attachment #1: Type: text/plain, Size: 1701 bytes --]


FYI, we noticed a +618 bytes kernel size regression due to commit:

commit: 0a2707446991f80336b8d89c942e498973d4793e (rcu/tiny: support reclaim for head-less object)
url: https://github.com/0day-ci/linux/commits/Uladzislau-Rezki-Sony/Introduce-kvfree_rcu-1-or-2-arguments/20200429-061752

Details as below (size data is obtained by `nm --size-sort vmlinux`):

02dabf68: rcu/tiny: move kvfree_call_rcu() out of header
0a270744: rcu/tiny: support reclaim for head-less object

+----------------------------+----------+----------+-------+
|           symbol           | 02dabf68 | 0a270744 | delta |
+----------------------------+----------+----------+-------+
| bzImage                    | 439392   | 439680   | 288   |
| nm.T.kvfree_call_rcu       | 5        | 209      | 204   |
| nm.T.rcu_init              | 25       | 157      | 132   |
| nm.t.kvfree_rcu_monitor    | 0        | 96       | 96    |
| nm.t.kvfree_rcu_work       | 0        | 81       | 81    |
| nm.b.monitor_work          | 0        | 44       | 44    |
| nm.b.rcu_work              | 0        | 28       | 28    |
| nm.t.rcu_process_callbacks | 146      | 153      | 7     |
| nm.T.call_rcu              | 46       | 51       | 5     |
| nm.b.kvcache               | 0        | 4        | 4     |
| nm.b.kvhead                | 0        | 4        | 4     |
| nm.b.kvhead_free           | 0        | 4        | 4     |
| nm.b.rcu_init_done         | 0        | 4        | 4     |
| nm.T.rcu_qs                | 36       | 40       | 4     |
| nm.b.monitor_todo          | 0        | 1        | 1     |
+----------------------------+----------+----------+-------+



Thanks,
Kbuild test robot


                 reply	other threads:[~2020-04-29  6:01 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=20200429060150.GA43416@04cb3a94dea8 \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 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.