Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: wgowcher@yahoo.com, Atsushi Nemoto <nemoto@toshiba-tops.co.jp>,
	linux-mips@oss.sgi.com
Subject: Re: Benchmark performance
Date: Thu, 16 Aug 2001 13:06:56 +0200	[thread overview]
Message-ID: <20010816130656.A18050@bacchus.dhis.org> (raw)
In-Reply-To: <005b01c12633$813c8820$0deca8c0@Ulysses>; from kevink@mips.com on Thu, Aug 16, 2001 at 11:11:56AM +0200

On Thu, Aug 16, 2001 at 11:11:56AM +0200, Kevin D. Kissell wrote:

> > Current CVS kernel uses FPU emulator unconditionally.  If one floating
> > point intruction causes a 'Unimplemented' exception (denormalized
> > result, etc.) following floating point instructions are also handle by
> > FPU emulator (not only the instruction which raise the exception).
> > 
> > I do not know this is really desired behavior, but here is a patch to
> > change this.  If Unimplemented exception had been occured during the
> > benchmark, aplying this patch may result better performance.
> 
> Not desired behavior, just an artifact.  However, I agree with Carsten
> that changing the API to the emulator for this and using a counter
> as you have done is not appropriate, and that the existing CPU
> configuration flag is a more appriate mechanism.  It's possible
> that Wayne's baseline numbers came from a pre-Algor-emulator
> kernel, and that this "feature" accounts for some of his degraded
> performance.  But I'd be surprised if it accounted for all of it,
> unless his FP test does 10% of its calculations on denormalized
> numbers or something.

As I don't know the exact nature of the calculations involved it may well
be that the broken behaviour of a pre-fpuemu kernel did completly break
the algorithem involved.

As for the hard-fp case I agree with you.  It would be interesting to
know if fp instructions that need emulation appear in groups.  Then it's
the (hopefully) rare case which we don't really care about.

  Ralf

  parent reply	other threads:[~2001-08-16 11:09 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 15:35 Problem with PMAD-AA / DECStation 5000/200 Armin F. Gnosa
2001-08-09 15:35 ` Armin F. Gnosa
2001-08-09 15:51 ` Florian Lohoff
2001-08-09 16:20   ` Jan-Benedict Glaw
2001-08-09 16:22     ` Martin Schulze
2001-08-09 16:35       ` Jan-Benedict Glaw
2001-08-10  9:00         ` Maciej W. Rozycki
2001-08-10  9:10           ` Jan-Benedict Glaw
2001-08-10  9:11     ` Maciej W. Rozycki
2001-08-10 13:32       ` Armin F. Gnosa
2001-08-10 13:32         ` Armin F. Gnosa
2001-08-13 11:30         ` Maciej W. Rozycki
2001-08-10  0:29   ` Problems mounting RedHat 7.0 or 7.1 from oss.sgi site Wayne Gowcher
2001-08-10  4:55     ` H . J . Lu
2001-08-13 17:34       ` Benchmark performance Wayne Gowcher
2001-08-13 17:34         ` Wayne Gowcher
2001-08-14  7:51         ` Ralf Baechle
2001-08-14 15:29           ` Wayne Gowcher
2001-08-16  3:56         ` Atsushi Nemoto
2001-08-16  7:43           ` Carsten Langgaard
2001-08-16  9:11           ` Kevin D. Kissell
2001-08-16  9:11             ` Kevin D. Kissell
2001-08-16 11:06             ` Ralf Baechle [this message]
2001-08-16 11:15             ` Atsushi Nemoto
2001-08-16  9:18           ` Ralf Baechle
2001-08-16 11:07             ` Carsten Langgaard
2001-08-16 11:14               ` Ralf Baechle
2001-08-24  9:06                 ` Atsushi Nemoto
2001-08-24 18:27                   ` Ralf Baechle
2001-08-10  8:54   ` Problem with PMAD-AA / DECStation 5000/200 Armin F. Gnosa
2001-08-10  8:54     ` Armin F. Gnosa
2001-08-10 10:33     ` Florian Lohoff
2001-08-12 20:32       ` Ralf Baechle
2001-08-12 20:40         ` Armin F. Gnosa
2001-08-12 20:40           ` Armin F. Gnosa
2001-08-12 20:41         ` Jan-Benedict Glaw
2001-08-13  9:58           ` Ralf Baechle

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=20010816130656.A18050@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=kevink@mips.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=nemoto@toshiba-tops.co.jp \
    --cc=wgowcher@yahoo.com \
    /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