From: Jun Sun <jsun@mvista.com>
To: Greg Lindahl <lindahl@keyresearch.com>
Cc: linux-mips@linux-mips.org, jsun@mvista.com
Subject: Re: [RFC] FPU context switch
Date: Tue, 17 Sep 2002 11:35:16 -0700 [thread overview]
Message-ID: <20020917113516.F17321@mvista.com> (raw)
In-Reply-To: <20020917113136.A1890@wumpus.internal.keyresearch.com>; from lindahl@keyresearch.com on Tue, Sep 17, 2002 at 11:31:36AM -0700
On Tue, Sep 17, 2002 at 11:31:36AM -0700, Greg Lindahl wrote:
> On Tue, Sep 17, 2002 at 11:04:23AM -0700, Jun Sun wrote:
>
> > Currently I am leaning towards 2) or 3). What is your opinion?
>
> (1) and (2) are how other archs like Alpha and Itanium deal with
> this. I think (3) is likely to be painful to debug
The good news is that I have already got it implemented and it
survived fairly stressful FPU tests. :-)
> and maintain and
> won't win much. So I'd suggest (2).
>
Yes, 3) is a little harder to maitain. I don't have much clue
as how much it will improve the performance in reality.
Presumably if there is only one FPU intensive process in the
system, it can improve a little bit.
Thanks for the feedback.
Jun
next prev parent reply other threads:[~2002-09-17 18:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 18:04 [RFC] FPU context switch Jun Sun
2002-09-17 18:31 ` Greg Lindahl
2002-09-17 18:35 ` Jun Sun [this message]
2002-09-17 18:42 ` justinca
2002-09-17 18:48 ` Jun Sun
2002-09-17 19:03 ` Greg Lindahl
2002-09-17 19:38 ` Daniel Jacobowitz
2002-09-17 21:44 ` Dominic Sweetman
2002-09-17 21:58 ` Matthew Dharm
2002-09-17 21:58 ` Matthew Dharm
2002-09-17 22:30 ` Kevin D. Kissell
2002-09-17 22:30 ` Kevin D. Kissell
2002-09-17 22:58 ` Greg Lindahl
2002-09-17 23:03 ` Jun Sun
2002-09-17 23:44 ` Kevin D. Kissell
2002-09-17 23:44 ` Kevin D. Kissell
2002-09-17 23:45 ` Jun Sun
2002-09-18 8:38 ` Kevin D. Kissell
2002-09-18 8:38 ` Kevin D. Kissell
2002-09-18 16:53 ` Jun Sun
2002-09-18 8:29 ` Carsten Langgaard
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=20020917113516.F17321@mvista.com \
--to=jsun@mvista.com \
--cc=lindahl@keyresearch.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.