From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Luis Chamberlain <mcgrof@kernel.org>,
Nick Alcock <nick.alcock@oracle.com>, <rostedt@goodmis.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Jiri Kosina <jikos@kernel.org>, Miroslav Benes <mbenes@suse.cz>,
Petr Mladek <pmladek@suse.com>,
Joe Lawrence <joe.lawrence@redhat.com>,
<live-patching@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Alexei Starovoitov <ast@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
<linux-modules@vger.kernel.org>, Ingo Molnar <mingo@redhat.com>,
David Laight <David.Laight@aculab.com>
Subject: Re: [PATCH v8 0/9] kallsyms: Optimizes the performance of lookup symbols
Date: Mon, 14 Nov 2022 09:25:43 +0800 [thread overview]
Message-ID: <61daf7e0-049c-0338-03a6-472694def181@huawei.com> (raw)
In-Reply-To: <Y3Bcs5sT17IcyQZD@bombadil.infradead.org>
On 2022/11/13 10:55, Luis Chamberlain wrote:
> On Sat, Nov 12, 2022 at 06:44:26PM -0800, Luis Chamberlain wrote:
>> On Wed, Nov 02, 2022 at 04:49:12PM +0800, Zhen Lei wrote:
>>> v7 --> v8:
>>> Sort the symbols by name and implement kallsyms_lookup_name() using a binary
>>> search. The performance is more than 20 times higher than that of v7. Of course,
>>> the memory overhead is also extended to (3 * kallsyms_num_syms) bytes. Discard
>>> all implementations of compression and then comparison in v7.
>>>
>>> In addition, all sparse warnings about kallsyms_selftest.c are cleared.
>>
>> Awesome work, I can't find a single thing I hate about this, but my
>> biggest conern is the lack of testing so I'm going to merge this to
>
> Sorry finished the email too fast, I just wanted to add Nick to the
> thread as his work does tons of changes on scripts/kallsyms.c.
>
> I was saying -- I'm just concern with the lack of testing so I have merged
> this to modules-next and see what explodes over the next few weeks.
> I'm also happy to drop this from modules-next and have it go through
> the livepatching tree instead, but given Nick's work is dedicated
> towards modules and it also touches on scripts/kallsyms.c a lot, to
> avoid conflicts it felt best to merge that to modules for now in case
> his changes get merged during the next merge window.
>
> Let me know what folks prefer.
>
> Obviously, if testing blows up we can drop the series.
>
> Zhen, wouldn't ftrace benefit from the same
> s/kallsyms_on_each_symbol/kallsyms_on_each_match_symbol ?
ftrace uses regular matching, so it cannot be replaced.
>
> Luis
> .
>
--
Regards,
Zhen Lei
prev parent reply other threads:[~2022-11-14 1:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 8:49 [PATCH v8 0/9] kallsyms: Optimizes the performance of lookup symbols Zhen Lei
2022-11-02 8:49 ` [PATCH v8 1/9] scripts/kallsyms: rename build_initial_tok_table() Zhen Lei
2022-11-02 8:49 ` [PATCH v8 2/9] kallsyms: Improve the performance of kallsyms_lookup_name() Zhen Lei
2022-11-02 8:49 ` [PATCH v8 3/9] kallsyms: Correctly sequence symbols when CONFIG_LTO_CLANG=y Zhen Lei
2022-11-02 8:49 ` [PATCH v8 4/9] kallsyms: Reduce the memory occupied by kallsyms_seqs_of_names[] Zhen Lei
2022-11-02 12:00 ` David Laight
2022-11-07 8:01 ` Leizhen (ThunderTown)
2022-11-02 8:49 ` [PATCH v8 5/9] kallsyms: Add helper kallsyms_on_each_match_symbol() Zhen Lei
2022-11-02 8:49 ` [PATCH v8 6/9] livepatch: Use kallsyms_on_each_match_symbol() to improve performance Zhen Lei
2022-11-23 13:28 ` Petr Mladek
2022-11-24 2:36 ` Leizhen (ThunderTown)
2022-11-24 8:29 ` Petr Mladek
2022-12-06 22:08 ` Luis Chamberlain
2022-12-07 1:30 ` Leizhen (ThunderTown)
2022-11-02 8:49 ` [PATCH v8 7/9] livepatch: Improve the search performance of module_kallsyms_on_each_symbol() Zhen Lei
2022-11-14 7:47 ` Jiri Olsa
2022-11-14 8:50 ` Leizhen (ThunderTown)
2022-11-14 9:27 ` Jiri Olsa
2022-11-14 10:00 ` Leizhen (ThunderTown)
2022-11-14 10:31 ` Jiri Olsa
2022-11-14 11:30 ` Leizhen (ThunderTown)
2022-11-14 13:26 ` Jiri Olsa
2022-11-14 15:46 ` Luis Chamberlain
2022-11-15 2:10 ` Leizhen (ThunderTown)
2022-11-15 7:30 ` Jiri Olsa
2022-11-15 7:54 ` Luis Chamberlain
2022-11-15 8:14 ` Leizhen (ThunderTown)
2022-11-15 20:11 ` Stephen Rothwell
2022-11-23 13:57 ` Petr Mladek
2022-11-24 2:41 ` Leizhen (ThunderTown)
2022-11-02 8:49 ` [PATCH v8 8/9] kallsyms: Delete an unused parameter related to kallsyms_on_each_symbol() Zhen Lei
2022-11-02 8:49 ` [PATCH v8 9/9] kallsyms: Add self-test facility Zhen Lei
2022-11-13 2:44 ` [PATCH v8 0/9] kallsyms: Optimizes the performance of lookup symbols Luis Chamberlain
2022-11-13 2:55 ` Luis Chamberlain
2022-11-14 1:25 ` Leizhen (ThunderTown) [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=61daf7e0-049c-0338-03a6-472694def181@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=David.Laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=ast@kernel.org \
--cc=jikos@kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=mingo@redhat.com \
--cc=nick.alcock@oracle.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.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).