From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: AES assembler optimizations
Date: Thu, 12 Aug 2004 16:18:11 -0400 [thread overview]
Message-ID: <cfgint$g8n$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <20040810133609.4f1ca352.davem@redhat.com>
David S. Miller wrote:
> On sparc64, we:
>
> 1) Always save the full FPU state at context switch time if it
> is active.
>
> 2) On entry to a FPU-using kernel routine, we save the FPU if
> it is active.
>
> 3) On exit from a FPU-using kernel routine, we do nothing
> except mark the FPU as inactive.
>
> 4) FPU-disabled traps by the user restore the state saved
> by #1 or #2
Depending on the cost saving of not saving the registers if they haven't
changed, vs. the time to take the trap and set the FPU active again, it
might be a win overall, even if you never used FPU in the kernel. Wasn't
there a change between saving everything and saving FPU only when used
"back when?" I seem to remember something about that, and the cost of
the test vs. the cost of just doing the save.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2004-08-12 20:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2riR3-7U5-3@gated-at.bofh.it>
2004-08-09 14:28 ` AES assembler optimizations Andi Kleen
2004-08-09 16:02 ` Bob Deblier
2004-08-09 17:12 ` Matti Aarnio
2004-08-10 19:51 ` H. Peter Anvin
2004-08-10 20:36 ` David S. Miller
2004-08-11 1:02 ` Paul Mackerras
2004-08-11 1:25 ` David S. Miller
2004-08-12 20:18 ` Bill Davidsen [this message]
2004-08-09 18:16 ` Andi Kleen
2004-08-09 20:20 ` dean gaudet
2004-08-09 13:47 Bob Deblier
2004-08-09 14:32 ` Patrick McFarland
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='cfgint$g8n$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.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 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.