From: Andrew McGregor <andrew@indranet.co.nz>
To: James Morris <jmorris@intercode.com.au>, linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@redhat.com>,
cryptoapi-devel <cryptoapi-devel@kerneli.org>
Subject: Re: [RFC] Hardware support notes for the kernel crypto API (2.5+)
Date: Sun, 15 Dec 2002 10:28:12 +1300 [thread overview]
Message-ID: <9000000.1039901292@localhost.localdomain> (raw)
In-Reply-To: <Mutt.LNX.4.44.0212150025190.24712-100000@blackbird.intercode.com.au>
> - What will the Kernel & Userspace APIs look like?
A socket family? Most userspace crypto apps, IMO, will deal with
networking somewhere.
> - Asymmetric crypto?
Yes please! A HiFn 6500 can do a 2048-bit DH exchange in about 30ms,
compared with several seconds for a P3-900. It's similarly fast for
everything else, and utterly astonishing for RSA (under a millisecond for a
signature!).
> Intel
> Crypto documentation for NICs unavailable.
I may have some leverage here. We'll see.
> Broadcom
> No response to emails.
But OpenBSD has drivers, and they say that Broadcom were very good to deal
with. I suggest writing the OpenBSD driver maintainer and asking who to
contact.
Andrew
next prev parent reply other threads:[~2002-12-14 21:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Mutt.LNX.4.44.0212150025190.24712-100000@blackbird.intercode.co m.au>
2002-12-14 13:51 ` [RFC] Hardware support notes for the kernel crypto API (2.5+) James Morris
2002-12-14 21:28 ` Andrew McGregor [this message]
2002-12-15 1:15 ` James Morris
2002-12-15 4:34 ` [CryptoAPI-devel] " Justin Clift
2002-12-17 16:54 ` Jean-Luc Cooke
2002-12-17 0:15 ` [CryptoAPI-devel] " Steve Isaacs
2002-12-17 0:56 ` Steve Isaacs
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=9000000.1039901292@localhost.localdomain \
--to=andrew@indranet.co.nz \
--cc=cryptoapi-devel@kerneli.org \
--cc=davem@redhat.com \
--cc=jmorris@intercode.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox