From: Andrew Jones <ajones@ventanamicro.com>
To: Amma Lee <lixiaoyun@binary-semi.com>
Cc: paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, xiezx@binary-semi.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: optimize ELF relocation function in riscv
Date: Mon, 3 Jul 2023 12:35:15 +0200 [thread overview]
Message-ID: <20230703-8fe42edab5ff83cea01db4f9@orel> (raw)
In-Reply-To: <1688355132-62933-1-git-send-email-lixiaoyun@binary-semi.com>
On Mon, Jul 03, 2023 at 11:32:12AM +0800, Amma Lee wrote:
> The patch can optimize the running times of insmod command by modify ELF
> relocation function.
> In the 5.10 and latest kernel, when install the riscv ELF drivers which
> contains multiple symbol table items to be relocated, kernel takes a lot
> of time to execute the relocation. For example, we install a 3+MB driver
> need 180+s.
> We focus on the riscv architecture handle R_RISCV_HI20 and R_RISCV_LO20
> type items relocation function in the arch\riscv\kernel\module.c and
> find that there are two-loops in the function. If we modify the begin
> number in the second for-loops iteration, we could save significant time
> for installation. We install the same 3+MB driver could just need 2s.
>
> Signed-off-by: Amma Lee <lixiaoyun@binary-semi.com>
> ---
> arch/riscv/kernel/module.c | 67 +++++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 64 insertions(+), 3 deletions(-)
>
I guess this is a v3 of [1]? But there's no change log here to know
what's different.
[1] 1683881513-18730-1-git-send-email-lixiaoyun@binary-semi.com
Thanks,
drew
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Jones <ajones@ventanamicro.com>
To: Amma Lee <lixiaoyun@binary-semi.com>
Cc: paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, xiezx@binary-semi.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: optimize ELF relocation function in riscv
Date: Mon, 3 Jul 2023 12:35:15 +0200 [thread overview]
Message-ID: <20230703-8fe42edab5ff83cea01db4f9@orel> (raw)
In-Reply-To: <1688355132-62933-1-git-send-email-lixiaoyun@binary-semi.com>
On Mon, Jul 03, 2023 at 11:32:12AM +0800, Amma Lee wrote:
> The patch can optimize the running times of insmod command by modify ELF
> relocation function.
> In the 5.10 and latest kernel, when install the riscv ELF drivers which
> contains multiple symbol table items to be relocated, kernel takes a lot
> of time to execute the relocation. For example, we install a 3+MB driver
> need 180+s.
> We focus on the riscv architecture handle R_RISCV_HI20 and R_RISCV_LO20
> type items relocation function in the arch\riscv\kernel\module.c and
> find that there are two-loops in the function. If we modify the begin
> number in the second for-loops iteration, we could save significant time
> for installation. We install the same 3+MB driver could just need 2s.
>
> Signed-off-by: Amma Lee <lixiaoyun@binary-semi.com>
> ---
> arch/riscv/kernel/module.c | 67 +++++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 64 insertions(+), 3 deletions(-)
>
I guess this is a v3 of [1]? But there's no change log here to know
what's different.
[1] 1683881513-18730-1-git-send-email-lixiaoyun@binary-semi.com
Thanks,
drew
next prev parent reply other threads:[~2023-07-03 10:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 3:32 [PATCH] riscv: optimize ELF relocation function in riscv Amma Lee
2023-07-03 3:32 ` Amma Lee
2023-07-03 10:35 ` Andrew Jones [this message]
2023-07-03 10:35 ` Andrew Jones
2023-07-03 10:47 ` Conor Dooley
2023-07-03 10:47 ` Conor Dooley
[not found] ` <7abf1c9c-c1b8-4b07-9be9-6a920fd5da6f.lixiaoyun@binary-semi.com>
2023-07-25 9:32 ` 回复:[PATCH] " Conor.Dooley
2023-07-25 9:32 ` Conor.Dooley
-- strict thread matches above, loose matches on Subject: below --
2023-05-10 11:10 [PATCH] " Amma.Lee
2023-05-11 22:45 ` Conor Dooley
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=20230703-8fe42edab5ff83cea01db4f9@orel \
--to=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lixiaoyun@binary-semi.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=xiezx@binary-semi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.