From: Arnd Bergmann <arnd@arndb.de>
To: James Morris <jmorris@intercode.com.au>
Cc: Thomas Spatzier <TSPAT@de.ibm.com>, <linux-kernel@vger.kernel.org>
Subject: Re: crypto API and IBM z990 hardware support
Date: Sun, 6 Jul 2003 19:46:41 +0200 [thread overview]
Message-ID: <200307061946.41991.arnd@arndb.de> (raw)
In-Reply-To: <Mutt.LNX.4.44.0307062353420.548-100000@excalibur.intercode.com.au>
On Sunday 06 July 2003 16:08, James Morris wrote:
> While this looks like it will work fine for the z990, it is a special case
> which does not address other requirements for hardware support (some
> initial requirements are listed at
> http://www.intercode.com.au/jamesm/crypto/hardware_notes.txt).
>
> I'm not enthusiastic about adding infrastructure which is really just a
> hack for some quaint hardware, and probably does not work towards
> addressing more common hardware requirements.
Ok, then I guess the module will simply have to declare MODULE_ALIAS("aes")
and live in arch/s390/crypto/, which means that the common code
is not touched at all, but building both the z990 assembler as well
as the C implementation as modules requires editing /etc/modprobe.conf
to get the right one.
As soon as you have the new API for crypto cards, we can move to that
for autoprobing the CPU features and reliably using the right
implementation.
Maybe you can add to your list something like the following items:
Requirements:
- Support for CPU specific optimized algorithms:
- autodetection of CPU features (e.g. Pentium MMX or z990 crypto)
- selection of different implementations. A high priority job
probably wants to use the CPU while another job offloads crypto
to an asynchronous add-on card.
Hardware Documentation status:
- IBM zSeries cryptographic instructions:
http://publibfp.boulder.ibm.com/cgi-bin/bookmgr/BOOKS/dz9zr002/7.5.25
GPL Driver status:
- IBM PCICC and PCICA cards (incompatible API):
Robert Burroughs <burrough@us.ibm.com>
http://oss.software.ibm.com/developerworks/opensource/linux390/june2003_recommended.shtml
- IBM zSeries cryptographic instructions:
Thomas Spatzier (work in progress)
Arnd <><
next prev parent reply other threads:[~2003-07-06 17:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4P45.5YN.11@gated-at.bofh.it>
[not found] ` <4T81.24d.41@gated-at.bofh.it>
2003-07-02 22:06 ` crypto API and IBM z990 hardware support Arnd Bergmann
2003-07-06 14:08 ` James Morris
2003-07-06 17:46 ` Arnd Bergmann [this message]
2003-07-07 7:14 ` Christoph Hellwig
2003-07-02 20:23 Ulrich Weigand
-- strict thread matches above, loose matches on Subject: below --
2003-07-02 12:35 Thomas Spatzier
2003-07-02 16:57 ` James Morris
2003-07-07 7:11 ` Christoph Hellwig
2003-07-07 10:27 ` James Morris
2003-07-02 7:07 Thomas Spatzier
2003-07-02 9:35 ` James Morris
2003-07-07 7:09 ` Christoph Hellwig
2003-07-08 2:53 ` David S. Miller
2003-07-08 3:37 ` Roland Dreier
2003-07-08 3:35 ` David S. Miller
2003-07-10 1:08 ` Werner Almesberger
2003-07-10 1:08 ` David S. Miller
2003-07-10 2:06 ` Werner Almesberger
2003-07-10 2:06 ` David S. Miller
2003-07-10 2:37 ` Werner Almesberger
2003-07-11 0:02 ` David S. Miller
[not found] ` <mailman.1057799700.15422.linux-kernel2news@redhat.com>
2003-07-10 5:55 ` Pete Zaitcev
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=200307061946.41991.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=TSPAT@de.ibm.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