public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Sami Tolvanen <samitolvanen@google.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
	Michal Marek <michal.lkml@markovi.net>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kbuild: reuse vmlinux.o in vmlinux_link
Date: Thu, 21 May 2020 15:18:37 -0700	[thread overview]
Message-ID: <202005211515.481BD90@keescook> (raw)
In-Reply-To: <20200521202716.193316-1-samitolvanen@google.com>

On Thu, May 21, 2020 at 01:27:16PM -0700, Sami Tolvanen wrote:
> Instead of linking all compilation units again each time vmlinux_link is
> called, reuse vmlinux.o from modpost_link.
> 
> With x86_64 allyesconfig, vmlinux_link is called three times and reusing
> vmlinux.o reduces the build time ~38 seconds on my system (59% reduction
> in the time spent in vmlinux_link).

BTW, I'll see this most in that it knocks about 6% off my "I changed
1 .c file and now I'm rebuilding" workflow time (which is obviously
dominated by linking), from 25 seconds to 23.5 seconds. And since most
of those seconds are spent staring at the build, it feels like a lot
more. ;)

-- 
Kees Cook

  parent reply	other threads:[~2020-05-21 22:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 20:27 [PATCH] kbuild: reuse vmlinux.o in vmlinux_link Sami Tolvanen
2020-05-21 22:08 ` Kees Cook
2020-05-22 18:16   ` Masahiro Yamada
2020-05-21 22:18 ` Kees Cook [this message]
2020-05-22 17:41 ` Masahiro Yamada
2020-05-22 17:44   ` Masahiro Yamada
2020-05-23 10:06     ` Nicholas Piggin
2020-05-23 15:12       ` Masahiro Yamada
2020-05-23 16:53         ` Sam Ravnborg
2020-05-25  6:13           ` Masahiro Yamada
2020-06-15 21:47         ` Sami Tolvanen
2020-06-16  3:22           ` 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=202005211515.481BD90@keescook \
    --to=keescook@chromium.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=samitolvanen@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox