From: Michal Ludvig <michal@logix.cz>
To: Andreas Happe <andreashappe@flatline.ath.cx>
Cc: James Morris <jmorris@redhat.com>,
cryptoapi@lists.logix.cz, linux-kernel@vger.kernel.org
Subject: Re: [cryptoapi/sysfs] display cipher details in sysfs
Date: Wed, 29 Sep 2004 15:13:58 +0200 [thread overview]
Message-ID: <415AB516.80108@logix.cz> (raw)
In-Reply-To: <20040928123426.GA21069@final-judgement.ath.cx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andreas Happe told me that:
> Michal Ludvig <michal@logix.cz> [040927 11:32]:
>
>> If I'd finally have two or more modules for the same algorithm loaded,
>> how
>> should the /sys subtree look like?
>
> good one.
>
> If there are lots of different implementation for a given algorithm it
> could be worthwhile to create a algorithm and a implementation -
> directory e.g.
>
> ls /sysfs/class/crypto/implementations would list:
> aes-i586 aes-c4 md5 sha1 sha256-c4
>
> and: ls /sysfs/class/crypto/algorithms
> aes
>
> with ls /sysfs/class/crypto/algorithms/aes
> name type implementations
>
> where implementations is a directory with links to the given
> implementations in /sysfs/class/crypto/implementations.
>
> Seems like a lot of work if there are only few implementations (like aes
> and aes-i586).
Once we have a support for hardware cryptocards it will be usefull. I'm
already having the VIA PadLock patch that adds yet another AES
implementation. For VIA C7 it will also support SHA (one module, two
algorithms? why not ;-)
IMHO it is worth having it done "right and expandable" since the
beginning (changing the /sys tree once it goes mainline will be harder).
Michal Ludvig
- --
* A mouse is a device used to point at the xterm you want to type in.
* Personal homepage - http://www.logix.cz/michal
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBWrUUDDolCcRbIhgRAqU7AKCCKEUplTD8PJldxT0yodC1M52UjQCg2DSx
Im6Amy3cGI+UhUqo4s/4IVk=
=fqyy
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-09-29 13:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040831175449.GA2946@final-judgement.ath.cx>
[not found] ` <Xine.LNX.4.44.0409010043020.30561-100000@thoron.boston.redhat.com>
2004-09-01 8:28 ` [cryptoapi/sysfs] display cipher details in sysfs Andreas Happe
2004-09-06 0:04 ` Greg KH
2004-09-07 16:37 ` James Morris
2004-09-07 16:45 ` Greg KH
2004-09-07 16:47 ` Michal Ludvig
2004-09-07 16:52 ` Greg KH
2004-09-06 18:49 ` Michal Ludvig
2004-09-07 14:35 ` Andreas Happe
2004-09-07 15:49 ` Michal Ludvig
2004-09-07 16:57 ` Andreas Happe
2004-09-10 11:21 ` Andreas Happe
2004-09-10 10:55 ` Andreas Happe
2004-09-27 8:41 ` Andreas Happe
2004-09-27 9:10 ` Michal Ludvig
2004-09-28 12:34 ` Andreas Happe
2004-09-29 9:36 ` Andreas Happe
2004-09-29 9:37 ` Andreas Happe
2004-09-29 14:13 ` Michal Ludvig
2004-09-29 13:13 ` Michal Ludvig [this message]
2004-09-27 15:53 ` James Morris
2004-09-28 12:21 ` [PATCH 2.6.9-rc2 1/2] cryptoapi: update sysfs-patch Andreas Happe
2004-09-28 12:23 ` [PATCH 2.6.9-rc2 2/2] cryptoapi: make /proc/crypto optional Andreas Happe
2004-09-28 14:32 ` Sven Schuster
2004-09-29 8:40 ` Andreas Happe
2004-09-07 16:36 ` [cryptoapi/sysfs] display cipher details in sysfs James Morris
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=415AB516.80108@logix.cz \
--to=michal@logix.cz \
--cc=andreashappe@flatline.ath.cx \
--cc=cryptoapi@lists.logix.cz \
--cc=jmorris@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox