From: Keith Owens <kaos@ocs.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] 2.5.8 sort kernel tables
Date: Sat, 20 Apr 2002 19:40:57 +1000 [thread overview]
Message-ID: <16993.1019295657@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Sat, 20 Apr 2002 09:50:53 +0100." <E16yqa5-0000Qs-00@the-village.bc.nu>
On Sat, 20 Apr 2002 09:50:53 +0100 (BST),
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> It requires extra storage which is unacceptable. The kernel tables
>> must be sorted before any code that might take an exception is used.
>> The sort must be done very early, before kernel memory management is
>> setup. In addition, the kernel stack has a limited size.
>
>Why not sort them after linking and before you boot the kernel. This sounds
>like a job for libbfd after link. I hadn't realised you planned to do the
>sort every boot
I considered that option but decided it was easier to sort the tables
at boot time.
Which tables to sort, where they are, the size of each entry, the size
and offset of the key in each table are all arch specific. The top
level makefile would have to make tmp_vmlinux then ask each arch
Makefile to do whatever it needed to convert tmp_vmlinux to vmlinux,
using a target specific program.
IA64 used to sort its unwind table at boot (ld was buggy at the time)
and the overhead was not noticable. PPC already sorts at boot time, I
doubt that they notice it. Either option would work but IMHO sorting
at boot time is easier to code and maintain.
next prev parent reply other threads:[~2002-04-20 9:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 11:38 Randal, Phil
2002-04-20 5:19 ` Keith Owens
2002-04-20 8:50 ` Alan Cox
2002-04-20 9:40 ` Keith Owens [this message]
[not found] <1589.1019123186@ocs3.intra.ocs.com.au.suse.lists.linux.kernel>
[not found] ` <15550.50131.489249.256007@nanango.paulus.ozlabs.org.suse.lists.linux.kernel>
2002-04-18 17:51 ` Andi Kleen
2002-04-18 23:17 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2002-04-18 9:46 Keith Owens
2002-04-18 10:21 ` Matthias Andree
2002-04-18 10:32 ` Keith Owens
2002-04-18 10:52 ` Alan Cox
2002-04-18 13:02 ` Paul Mackerras
2002-04-18 15:38 ` Keith Owens
2002-04-18 15:52 ` Russell King
2002-04-18 16:09 ` Keith Owens
2002-04-18 13:59 ` William Lee Irwin III
2002-04-18 18:16 ` Kai Henningsen
2002-04-18 18:24 ` William Lee Irwin III
2002-04-19 11:46 ` David Weinehall
2002-04-18 20:20 ` Oliver Xymoron
2002-04-19 4:59 ` Matt
2002-04-19 13:45 ` Jamie Lokier
2002-04-19 13:46 ` Jamie Lokier
2002-04-19 14:25 ` Oliver Xymoron
2002-04-19 15:16 ` Tobias Wollgam
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=16993.1019295657@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®