From: "Arnd Bergmann" <arnd@arndb.de>
To: "Rong Xu" <xur@google.com>, "Arnd Bergmann" <arnd@kernel.org>
Cc: linux-kbuild@vger.kernel.org,
"Masahiro Yamada" <masahiroy@kernel.org>,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
"Han Shen" <shenhan@google.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Kees Cook" <kees@kernel.org>, "Jann Horn" <jannh@google.com>,
"Ard Biesheuvel" <ardb@kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] [RFC, DO NOT APPLY] vmlinux.lds: revert link speed regression
Date: Tue, 21 Jan 2025 22:17:50 +0100 [thread overview]
Message-ID: <c5855908-df1f-46be-a8cf-aba066b52585@app.fastmail.com> (raw)
In-Reply-To: <CAF1bQ=QFxE8AvnpOeSjSeL1buxDDACKVNufLjw99cQir0pyS_Q@mail.gmail.com>
On Tue, Jan 21, 2025, at 18:45, Rong Xu wrote:
> On Mon, Jan 20, 2025 at 1:29 PM Arnd Bergmann <arnd@kernel.org> wrote:
>
> Yes. The order could be conditional. As a matter of fact, the first
> version was conditional.
> I changed it based on the reviewer comments to reduce conditions for
> more maintainable code.
> I would like to work from the ld.bfd side to see if we can fix the problem.
Makes sense. At least once we understand what makes the linker so slow
and fix future versions, it should also be possible to come up with
a more effective workaround for the existing linkers that suffer from it.
Arnd
next prev parent reply other threads:[~2025-01-21 21:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 21:21 [PATCH] [RFC, DO NOT APPLY] vmlinux.lds: revert link speed regression Arnd Bergmann
2025-01-21 0:19 ` Masahiro Yamada
2025-01-21 7:41 ` Arnd Bergmann
2025-01-21 17:36 ` Rong Xu
2025-01-21 17:45 ` Rong Xu
2025-01-21 21:17 ` Arnd Bergmann [this message]
2025-01-22 18:47 ` Rong Xu
2025-01-22 20:29 ` Arnd Bergmann
2025-01-22 22:37 ` Rong Xu
-- strict thread matches above, loose matches on Subject: below --
2025-01-22 23:59 Sam James
2025-01-23 7:33 ` Arnd Bergmann
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=c5855908-df1f-46be-a8cf-aba066b52585@app.fastmail.com \
--to=arnd@arndb.de \
--cc=ardb@kernel.org \
--cc=arnd@kernel.org \
--cc=jannh@google.com \
--cc=kees@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=shenhan@google.com \
--cc=xur@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