From: Jun Sun <jsun@mvista.com>
To: linux-mips@linux-mips.org
Cc: jsun@mvista.com
Subject: [jsun@mvista.com: Re: [RFC] FPU context switch]
Date: Tue, 17 Sep 2002 16:04:25 -0700 [thread overview]
Message-ID: <20020917160425.O17321@mvista.com> (raw)
Meant to send to the list ....
----- Forwarded message from Jun Sun <jsun@mvista.com> -----
X-Sieve: cmu-sieve 2.0
Date: Tue, 17 Sep 2002 16:02:26 -0700
From: Jun Sun <jsun@mvista.com>
To: Greg Lindahl <lindahl@keyresearch.com>
Cc: jsun@mvista.com
Subject: Re: [RFC] FPU context switch
User-Agent: Mutt/1.2.5i
In-Reply-To: <20020917155854.B1883@wumpus.attbi.com>; from lindahl@keyresearch.com on Tue, Sep 17, 2002 at 03:58:54PM -0700
On Tue, Sep 17, 2002 at 03:58:54PM -0700, Greg Lindahl wrote:
> On Wed, Sep 18, 2002 at 12:30:23AM +0200, Kevin D. Kissell wrote:
>
> > I'm extremely skeptical about this "evidence".
>
> The only good test is Linux with and without lazy saves. Throwing in a
> new OS complicates matters. It sounds like Jun already has working
> code for (1) and (3), so he can do a good test.
>
I actually have 2) and 3). 1) is easy to do, though.
Anyone can recommand some test programs to try?
A while back, I tried lmbench which is not very telling.
I think the reason is that most of the tests are not using
FPU at all.
However I might try it again anyway. It might tell the
difference between 1) and 2)&3) easily.
Jun
----- End forwarded message -----
next reply other threads:[~2002-09-17 23:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 23:04 Jun Sun [this message]
2002-09-18 0:10 ` [jsun@mvista.com: Re: [RFC] FPU context switch] Kevin D. Kissell
2002-09-18 0:10 ` Kevin D. Kissell
2002-09-18 0:14 ` Jun Sun
2002-09-18 8:45 ` Kevin D. Kissell
2002-09-18 8:45 ` Kevin D. Kissell
2002-09-18 16:57 ` Jun Sun
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=20020917160425.O17321@mvista.com \
--to=jsun@mvista.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.