From: Jessica Yu <jeyu@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: rusty@rustcorp.com.au, Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: module: Optimize search_module_extables()
Date: Fri, 10 Feb 2017 23:41:34 -0500 [thread overview]
Message-ID: <20170211044133.GA2879@packer-debian-8-amd64.digitalocean.com> (raw)
In-Reply-To: <20170208144801.GZ6515@twins.programming.kicks-ass.net>
+++ Peter Zijlstra [08/02/17 15:48 +0100]:
>
>While looking through the __ex_table stuff I found that we do a linear
>lookup of the module. Also fix up a comment.
>
>Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Applied, thanks.
Hm. A quick scan through module.c still shows a couple of places that use
similar linear lookups, and may benefit from the same __module_address
optimization. But I'll save that for a separate patch..
Jessica
>---
> kernel/module.c | 27 ++++++++++++++-------------
> 1 file changed, 14 insertions(+), 13 deletions(-)
>
>diff --git a/kernel/module.c b/kernel/module.c
>index 3d8f126208e3..7bcdc35dbf95 100644
>--- a/kernel/module.c
>+++ b/kernel/module.c
>@@ -4165,22 +4165,23 @@ const struct exception_table_entry *search_module_extables(unsigned long addr)
> struct module *mod;
>
> preempt_disable();
>- list_for_each_entry_rcu(mod, &modules, list) {
>- if (mod->state == MODULE_STATE_UNFORMED)
>- continue;
>- if (mod->num_exentries == 0)
>- continue;
>+ mod = __module_address(addr);
>+ if (!mod)
>+ goto out;
>
>- e = search_extable(mod->extable,
>- mod->extable + mod->num_exentries - 1,
>- addr);
>- if (e)
>- break;
>- }
>+ if (!mod->num_exentries)
>+ goto out;
>+
>+ e = search_extable(mod->extable,
>+ mod->extable + mod->num_exentries - 1,
>+ addr);
>+out:
> preempt_enable();
>
>- /* Now, if we found one, we are running inside it now, hence
>- we cannot unload the module, hence no refcnt needed. */
>+ /*
>+ * Now, if we found one, we are running inside it now, hence
>+ * we cannot unload the module, hence no refcnt needed.
>+ */
> return e;
> }
>
prev parent reply other threads:[~2017-02-11 4:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 14:48 [PATCH] module: Optimize search_module_extables() Peter Zijlstra
2017-02-08 15:44 ` Mark Rutland
2017-02-11 4:41 ` Jessica Yu [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=20170211044133.GA2879@packer-debian-8-amd64.digitalocean.com \
--to=jeyu@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peterz@infradead.org \
--cc=rusty@rustcorp.com.au \
/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