From: Arjan van de Ven <arjan@infradead.org>
To: "Peter Teoh" <htmldeveloper@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, "Sam Ravnborg" <sam@ravnborg.org>
Subject: Re: A question sort_main_extable()
Date: Thu, 20 Nov 2008 21:47:17 -0800 [thread overview]
Message-ID: <20081120214717.1a02a9af@infradead.org> (raw)
In-Reply-To: <804dabb00811202142y799fb70dxf89a1fc3514d78b1@mail.gmail.com>
On Fri, 21 Nov 2008 13:42:56 +0800
"Peter Teoh" <htmldeveloper@gmail.com> wrote:
> Inside start_kernel() there is a call to sort_main_extable().
>
> void sort_extable(struct exception_table_entry *start,
> struct exception_table_entry *finish)
> {
> sort(start, finish - start, sizeof(struct
> exception_table_entry), cmp_ex, NULL);
> }
>
> With reference to
> http://tuxology.net/2008/07/08/benchmarking-boot-latency-on-x86/, I
> think it can help bootup latency (how much I got no number) if the
> sorting is done post-compilation time, instead of dynamically
> everytime the system bootup. (perhaps at the stage of modposting,
> when all the vmlinux, kernel modules objects have been generated, so
> extracting out the exceptions strings is possible?) Is this a
> possible optimization?
we used to do this but it was a pain and extremely fragile. Runtime
sorting makes it very robust at least.
The sort is really quick though; I've spent a lot of time on boot time
and this guy never showed up for me.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-11-21 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 5:42 A question sort_main_extable() Peter Teoh
2008-11-21 5:47 ` Arjan van de Ven [this message]
2008-11-21 6:43 ` Peter Teoh
2008-11-23 19:45 ` Andi Kleen
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=20081120214717.1a02a9af@infradead.org \
--to=arjan@infradead.org \
--cc=htmldeveloper@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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 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.