From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, lkp@intel.com,
Josh Triplett <josh@joshtriplett.org>
Subject: [lkp] [+364 bytes kernel size regression] [i386-tinyconfig] [d68fc4d5da] xattr: use rbtree for simple_xattrs
Date: Mon, 7 Nov 2022 22:20:09 +0800 [thread overview]
Message-ID: <Y2kUGUXN2DF0M159@2d882e5f7ced> (raw)
In-Reply-To: <20221107133540.1503822-1-brauner@kernel.org>
FYI, we noticed a +364 bytes kernel size regression due to commit:
commit: d68fc4d5da695b25e5580d96fafc8ab7bb4b1fc5 (xattr: use rbtree for simple_xattrs)
url: https://github.com/intel-lab-lkp/linux/commits/Christian-Brauner/xattr-use-rbtree-for-simple_xattrs/20221107-213723
patch link: https://lore.kernel.org/linux-fsdevel/20221107133540.1503822-1-brauner@kernel.org
patch subject: [PATCH] xattr: use rbtree for simple_xattrs
Details as below (size data is obtained by `nm --size-sort vmlinux`):
9abf2313: Linux 6.1-rc1
d68fc4d5: xattr: use rbtree for simple_xattrs
+-------------------------------+----------+----------+-------+
| symbol | 9abf2313 | d68fc4d5 | delta |
+-------------------------------+----------+----------+-------+
| nm.T.simple_xattr_get | 75 | 217 | 142 |
| bzImage | 491520 | 491648 | 128 |
| nm.T.simple_xattr_set | 256 | 314 | 58 |
| nm.T.simple_xattrs_free | 0 | 49 | 49 |
| nm.t.put_simple_xattr_rcu | 0 | 42 | 42 |
| nm.T.simple_xattr_add | 0 | 40 | 40 |
| nm.t.free_simple_xattr | 0 | 23 | 23 |
| nm.T.simple_xattrs_init | 0 | 14 | 14 |
| nm.T.simple_xattr_alloc | 49 | 56 | 7 |
| nm.t.free_simple_xattr_rcu_cb | 0 | 2 | 2 |
| nm.D.linux_banner | 152 | 153 | 1 |
| nm.T.simple_xattr_list | 94 | 93 | -1 |
| nm.T.simple_xattr_list_add | 13 | 0 | -13 |
+-------------------------------+----------+----------+-------+
Thanks
prev parent reply other threads:[~2022-11-07 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 13:35 [PATCH] xattr: use rbtree for simple_xattrs Christian Brauner
2022-11-07 14:20 ` kernel test robot [this message]
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=Y2kUGUXN2DF0M159@2d882e5f7ced \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=josh@joshtriplett.org \
--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.