From: "Arnd Bergmann" <arnd@arndb.de>
To: "Masahiro Yamada" <masahiroy@kernel.org>, "Jann Horn" <jannh@google.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Miguel Ojeda" <ojeda@kernel.org>,
"Zhen Lei" <thunder.leizhen@huawei.com>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 2/2] kallsyms: build faster by using .incbin
Date: Thu, 22 Feb 2024 09:20:26 +0100 [thread overview]
Message-ID: <d419dc3f-ce85-4bae-bb93-05e0103a1c6c@app.fastmail.com> (raw)
In-Reply-To: <CAK7LNAQG_dX8p0Lch-wg8cOVRQzaJUh2zFJL+3tgpcT8_iSTow@mail.gmail.com>
On Thu, Feb 22, 2024, at 05:06, Masahiro Yamada wrote:
> On Thu, Feb 22, 2024 at 5:27 AM Jann Horn <jannh@google.com> wrote:
>> This change reduces the time for an incremental kernel rebuild
>> (touch fs/ioctl.c, then re-run make) from 27.7s to 24.1s (medians
>> over 16 runs each) on my machine - saving around 3.6 seconds.
Nice!
...
> This reverts bea5b74504742f1b51b815bcaf9a70bddbc49ce3
>
> Somebody might struggle with debugging again, but I am not sure.
>
> Arnd?
So far, I have not needed it again, but it's only been a year.
> If the effort were "I invented a way to do kallsyms in
> one pass instead of three", it would be so much more attractive.
>
>
> I am not so sure if this grain of the optimization is exciting,
> but I confirmed that a few seconds were saved for the defconfig.
>
> I am neutral about this.
I think the time savings are worth it, especially since this
is going to help anyone building on large machines where
the compile stage is already optimized a lot but the link
stage is limited by single-thread performance.
Arnd
next prev parent reply other threads:[~2024-02-22 8:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 20:26 [PATCH 1/2] kallsyms: get rid of code for absolute kallsyms Jann Horn
2024-02-21 20:26 ` [PATCH 2/2] kallsyms: build faster by using .incbin Jann Horn
2024-02-21 20:29 ` Jann Horn
2024-02-22 4:06 ` Masahiro Yamada
2024-02-22 8:20 ` Arnd Bergmann [this message]
2024-02-22 11:20 ` Jann Horn
2024-02-22 14:20 ` Jann Horn
2024-02-23 4:26 ` Masahiro Yamada
2024-02-21 21:18 ` [PATCH 1/2] kallsyms: get rid of code for absolute kallsyms Arnd Bergmann
2024-02-23 12:33 ` 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=d419dc3f-ce85-4bae-bb93-05e0103a1c6c@app.fastmail.com \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=jannh@google.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=thunder.leizhen@huawei.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
all inboxes | Powered by JetHome®