mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jingbo Xu <jefflexu@linux.alibaba.com>
To: linux-kbuild@vger.kernel.org, masahiroy@kernel.org,
	nathan@kernel.org, ndesaulniers@google.com, nicolas@fjasle.eu
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [MAYBE REGRESSION] kbuild time of kernel compiling
Date: Mon, 22 Jan 2024 16:32:26 +0800	[thread overview]
Message-ID: <be1abcda-4cf0-4441-9a27-831eaef28f2e@linux.alibaba.com> (raw)

Hi,

I noticed a regression of kbuild time in v6.7, especially when running
`make` command when all images have already been compiled.  In v6.6 it
takes ~3s, while in v6.7 it takes ~18s.

I'm not sure if it's a known issue, or an extra action configurable with
a "CONFIG_XX" option.


Following is the kbuild time in v6.6 versus v7.7, with
arch/x86/configs/x86_64_defconfig used here:


v6.6
```
make clean
make olddefconfig

# first full compiling
$time make bzImage -j128 -s

real	1m9.896s
user	36m56.153s
sys	4m21.748s

# second time with image already compiled
$time make bzImage -j128 -s

real	0m2.776s
user	0m13.823s
sys	0m3.936s
```


v6.7
```
make clean
make olddefconfig

# first full compiling
$time make bzImage -j128 -s

real	1m22.865s
user	37m25.977s
sys	4m22.094s

# second time with image already compiled
$time make bzImage -j128 -s

real	0m18.209s
user	0m29.243s
sys	0m4.330s
```


I tried to bisect, while commit d4e175f2c460 ("Merge tag 'vfs-6.7.super'
of gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs") is identified
as the first bad commit, which is obviously wrong.  As I'm not familiar
with the structure of the merge commit, the further investigation has
not been made yet.


Besides, it seems that it will take most of the time before "CALL
scripts/checksyscalls.sh" is printed (with "INSTALL libsubcmd_headers"
has already printed).

$time make bzImage -j128
  DESCEND objtool
  INSTALL libsubcmd_headers

  CALL    scripts/checksyscalls.sh
  BUILD   arch/x86/boot/bzImage
Kernel: arch/x86/boot/bzImage is ready  (#437)

-- 
Thanks,
Jingbo

             reply	other threads:[~2024-01-22  8:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22  8:32 Jingbo Xu [this message]
2024-01-22 10:50 ` Linux regression tracking (Thorsten Leemhuis)
2024-01-22 13:34   ` Jingbo Xu
2024-01-22 12:21 ` Masahiro Yamada

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=be1abcda-4cf0-4441-9a27-831eaef28f2e@linux.alibaba.com \
    --to=jefflexu@linux.alibaba.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®