From: Jason Wessel <jason.wessel@windriver.com>
To: Alessio Igor Bogani <abogani@kernel.org>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
LKML <linux-kernel@vger.kernel.org>,
Tim Bird <tim.bird@am.sony.com>
Subject: Re: [PATCH] module: Use the binary search for symbols resolution
Date: Thu, 07 Apr 2011 08:49:28 -0500 [thread overview]
Message-ID: <4D9DC0E8.5080705@windriver.com> (raw)
In-Reply-To: <1302024146-2608-2-git-send-email-abogani@kernel.org>
On 04/05/2011 12:22 PM, Alessio Igor Bogani wrote:
> Let the linker sort the exported symbols and use the binary search for locate them.
>
It would be nice if this patch header included some of the information from introduction message, that asside the technical content looks good.
> This work was supported by a hardware donation from the CE Linux Forum.
>
> Signed-off-by: Alessio Igor Bogani <abogani@kernel.org>
Reviewed-by: Jason Wessel <jason.wessel@windriver.com>
> static bool find_symbol_in_section(const struct symsearch *syms,
> struct module *owner,
> unsigned int symnum, void *data)
> {
> struct find_symbol_arg *fsa = data;
>
> - if (strcmp(syms->start[symnum].name, fsa->name) != 0)
> - return false;
> -
> if (!fsa->gplok) {
> if (syms->licence == GPL_ONLY)
> return false;
This was the only part I had a hard time following, but after having looked at the original source to kernel/module.c, I see how this was optimized and agree.
This looks like a very nice speed up for large interdependent kernel modules.
Cheers,
Jason.
next prev parent reply other threads:[~2011-04-07 13:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 17:22 [PATCH] Speed up the symbols' resolution process V2 Alessio Igor Bogani
2011-04-05 17:22 ` [PATCH] module: Use the binary search for symbols resolution Alessio Igor Bogani
2011-04-07 13:49 ` Jason Wessel [this message]
2011-04-12 3:48 ` Rusty Russell
2011-04-12 22:36 ` Anders Kaseorg
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=4D9DC0E8.5080705@windriver.com \
--to=jason.wessel@windriver.com \
--cc=abogani@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=tim.bird@am.sony.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.