From: Peter Osterlund <petero2@telia.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andi Kleen <ak@colin2.muc.de>, Andi Kleen <ak@muc.de>,
Andrew Morton <akpm@osdl.org>,
jh@suse.cz, Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add noinline attribute
Date: 16 Jan 2004 01:26:10 +0100 [thread overview]
Message-ID: <m2u12wn3h9.fsf@p4.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0401151448200.2597@evo.osdl.org>
Linus Torvalds <torvalds@osdl.org> writes:
> On Wed, 15 Jan 2004, Andi Kleen wrote:
> >
> > That's fine for me. In fact I did this some time ago on x86-64 when I
> > ran into similar problems. Here's a port of the x86-64 sort function.
>
> Ugh. Can't we just make this be generic code (and that means calling it in
> the module loading code too..)?
>
> As to bubble sort (which is fine for something that is 99% sorted anyway),
> isn't it better to continue pushing the entry down when you find something
> out of order? That way you don't have to repeat the whole scan, you just
> continue with the next entry once the unsorted entry has percolated to its
> place (ie keep entries "0..n-1" sorted at all times). That should make the
> code cleaner too.
Yes, that algorithm is called insertion sort and is already
implemented in the ppc arch.
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
next prev parent reply other threads:[~2004-01-16 0:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 8:31 Andi Kleen
2004-01-14 23:23 ` Linus Torvalds
2004-01-15 7:48 ` Andi Kleen
2004-01-15 22:55 ` Linus Torvalds
2004-01-16 0:26 ` Peter Osterlund [this message]
2004-01-16 10:13 ` Andi Kleen
2004-01-18 20:47 ` Richard Henderson
2004-01-18 20:58 ` Andi Kleen
2004-01-19 0:41 ` Richard Henderson
2004-01-18 23:07 ` [PATCH] Add noinline attribute - new extable sort patch Andi Kleen
2004-01-19 0:52 ` Richard Henderson
2004-01-19 1:01 ` Andi Kleen
2004-01-19 11:26 ` Rusty Russell
2004-01-15 0:35 ` [PATCH] Add noinline attribute Rusty Russell
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=m2u12wn3h9.fsf@p4.localdomain \
--to=petero2@telia.com \
--cc=ak@colin2.muc.de \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=jh@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®