public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: Kai Henningsen <kaih@khms.westfalen.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] 2.5.8 sort kernel tables
Date: Fri, 19 Apr 2002 13:46:35 +0200	[thread overview]
Message-ID: <20020419134635.D22790@khan.acc.umu.se> (raw)
In-Reply-To: <1589.1019123186@ocs3.intra.ocs.com.au> <1589.1019123186@ocs3.intra.ocs.com.au> <20020418135931.GU21206@holomorphy.com> <8N7App8mw-B@khms.westfalen.de>

On Thu, Apr 18, 2002 at 08:16:00PM +0200, Kai Henningsen wrote:
> wli@holomorphy.com (William Lee Irwin III)  wrote on 18.04.02 in <20020418135931.GU21206@holomorphy.com>:
> 
> > On Thu, Apr 18, 2002 at 07:46:26PM +1000, Keith Owens wrote:
> > > The use of __init and __exit sections breaks the assumption that tables
> > > such as __ex_table are sorted, it has already broken the dbe table in
> > > mips on 2.5.  This patch against 2.5.8 adds a generic sort routine and
> > > sorts the i386 exception table.
> > > This sorting needs to be extended to several other tables, to all
> > > architectures, to modutils (insmod loads some of these tables for
> > > modules) and back ported to 2.4.  Before I spend the rest of the time,
> > > any objections?
> >
> > It doesn't have to be an O(n lg(n)) method but could you use something
> > besides bubblesort? Insertion sort, selection sort, etc. are just as
> > easy and they don't have the horrific stigma of being "the worst sorting
> > algorithm ever" etc.
> 
> Surely the worst (working) sort is randomsort? (Check if sorted. If not,  
> pick two entries at random, exchange, retry.)

I've always been a fan of bit-decay sort.

while (!sorted(data))
	;


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Maintainer of the v2.0 kernel   //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  parent reply	other threads:[~2002-04-19 11:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18  9:46 [RFC] 2.5.8 sort kernel tables 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 [this message]
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
     [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-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

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=20020419134635.D22790@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=kaih@khms.westfalen.de \
    --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