From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Alexander Lobakin <alobakin@pm.me>
Cc: Nathan Chancellor <natechancellor@gmail.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Rapoport <rppt@kernel.org>,
Jinyang He <hejinyang@loongson.cn>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH mips-next 0/2] MIPS: optimize relocations processing
Date: Mon, 18 Jan 2021 15:57:58 +0100 [thread overview]
Message-ID: <20210118145758.GB11749@alpha.franken.de> (raw)
In-Reply-To: <20210116150126.20693-1-alobakin@pm.me>
On Sat, Jan 16, 2021 at 03:01:57PM +0000, Alexander Lobakin wrote:
> This series converts the logics of two main relocation functions,
> one for relocatable kernel and one for modules, from the arrays of
> handlers (callbacks) to plain switch-case functions, which allows
> the compiler to greatly optimize the code, so the relocations will
> be applied faster with lesser code size.
>
> Tested on MIPS32 R2 with GCC 10.2 and LLVM 11.0 with -O2.
>
> Alexander Lobakin (2):
> MIPS: module: optimize module relocations processing
> MIPS: relocatable: optimize the relocation process
>
> arch/mips/kernel/module.c | 109 +++++++++++++++++-------------------
> arch/mips/kernel/relocate.c | 54 ++++++++++--------
> 2 files changed, 82 insertions(+), 81 deletions(-)
series applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-01-18 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 15:01 [PATCH mips-next 0/2] MIPS: optimize relocations processing Alexander Lobakin
2021-01-16 15:02 ` [PATCH mips-next 1/2] MIPS: module: optimize module " Alexander Lobakin
2021-01-16 15:02 ` [PATCH mips-next 2/2] MIPS: relocatable: optimize the relocation process Alexander Lobakin
2021-01-18 1:49 ` [PATCH mips-next 1/2] MIPS: module: optimize module relocations processing Jiaxun Yang
2021-01-18 14:57 ` Thomas Bogendoerfer [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=20210118145758.GB11749@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=akpm@linux-foundation.org \
--cc=alobakin@pm.me \
--cc=hejinyang@loongson.cn \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=rppt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).