From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] The $200 walmart "gPC"
Date: Fri, 1 Feb 2008 11:41:28 +0000 [thread overview]
Message-ID: <c99bcd8b9c9a8b33de038a45ab1121ff@terzarima.net> (raw)
In-Reply-To: <4f34febc0801312147x1d490b50y85e2a344514951d8@mail.gmail.com>
> What would be involved in patching Plan 9's libsec to use
> the C7's crypto instructions?
it didn't look too hard, but there's a bit of work to do in the kernel
to enable it (and enable sse for some instructions).
are there similar things on intel and amd? i haven't really kept up.
no doubt they all use different instructions and conventions so
we'll need an array of implementations.
next prev parent reply other threads:[~2008-02-01 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 5:33 ron minnich
2008-02-01 5:47 ` John Barham
2008-02-01 11:19 ` Pietro Gagliardi
2008-02-01 11:41 ` Charles Forsyth [this message]
2008-02-01 17:04 ` ron minnich
2008-02-01 11:43 ` Charles Forsyth
2008-02-01 12:00 ` mattmobile
2008-02-01 12:12 ` erik quanstrom
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=c99bcd8b9c9a8b33de038a45ab1121ff@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).