From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Duron kernel crash (i686 works)
Date: Wed, 12 Sep 2001 11:09:50 -0700 [thread overview]
Message-ID: <20010912110950.D25683@mikef-linux.matchmail.com> (raw)
In-Reply-To: <E15h9RE-0004Qe-00@the-village.bc.nu> <2415359415.20010912164800@port.imtp.ilyichevsk.odessa.ua>
In-Reply-To: <2415359415.20010912164800@port.imtp.ilyichevsk.odessa.ua>
On Wed, Sep 12, 2001 at 04:48:00PM +0300, VDA wrote:
> >> A better way to do it is to bencmark several routines at
> >> startup time and pick the best one. It is done now
> >> for RAID xor'ing routine.
> AC> Not in this case. It is Athlon specific code. It was fine
> AC> tuned when it was written
> Yes, but sometimes we have routines which perform
> differently on different CPUs. See inslude/asm-i386/string.h
> and string-486.h: on Pentium rep movsd is faster, on 386 unrolled
> loop is faster... so optimal routine can be picked only at runtime.
> CPU-specific routines can compete in such runtime benchmark
> too when proper processor is detected - see how KNI-specific
> RAID xor routine does that.
Hmm, just how far do you want to take that? Compile in all of the
optimizations and test which is fastest on each processor at startup?
Hmm, that might not be a bad idea for dev kernels, as it might show
optimization problems on certain processors...
next prev parent reply other threads:[~2001-09-12 18:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-11 1:11 Duron kernel crash (i686 works) Roberto Jung Drebes
2001-09-11 3:30 ` Roberto Jung Drebes
2001-09-11 14:47 ` Alan Cox
2001-09-12 6:59 ` VDA
2001-09-12 10:51 ` Steffen Persvold
2001-09-12 11:08 ` VDA
2001-09-12 11:23 ` Arjan van de Ven
2001-09-12 12:48 ` Alan Cox
2001-09-12 13:48 ` VDA
2001-09-12 18:09 ` Mike Fedyk [this message]
[not found] <154763769.20010911115644@port.imtp.ilyichevsk.odessa.ua>
2001-09-11 19:38 ` Roberto Jung Drebes
2001-09-12 6:56 ` Liakakis Kostas
2001-09-12 8:21 ` Morten Helgesen
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=20010912110950.D25683@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--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