From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: linux-crypto@vger.kernel.org
Cc: Sebastian Siewior <linux-crypto@ml.breakpoint.cc>
Subject: Re: [1/1] HIFN: preliminary HIFN 795x driver for new async cryptoapi.
Date: Wed, 23 May 2007 12:03:54 +0400 [thread overview]
Message-ID: <20070523080354.GA19665@2ka.mipt.ru> (raw)
In-Reply-To: <20070522151919.GB32493@Chamillionaire.breakpoint.cc>
On Tue, May 22, 2007 at 05:19:19PM +0200, Sebastian Siewior (linux-crypto@ml.breakpoint.cc) wrote:
> * Evgeniy Polyakov | 2007-05-22 16:58:29 [+0400]:
>
> >Current driver only supports AES ECB encrypt/decrypt, since I do not
> >know how to detect operation mode in runtime (a question).
> Take a look on my skeleton driver (posted just a few seconds ago). It
> should solve your problem here.
It does not - your code only supposed to work with ecb, since it is what
was requested during initialization time. This new scheme with templates
helps alot for ciphers/crypto modes which do not support several
templates, so I used old scheme with 'cipher' only template, not
'ecb(cipher)', 'cbc(cipher)' and so on.
And, btw, do not use mutex in encryption path, it is not supposed to
sleep in ipsec.
HIFN supports at least 12 different ciphers/mode (3des, des and aes,
each one with 4 modes), so it is not a good idea to put them all into
separated structures, so I rised a question about it.
> Sebastian
--
Evgeniy Polyakov
next prev parent reply other threads:[~2007-05-23 8:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 12:58 [1/1] HIFN: preliminary HIFN 795x driver for new async cryptoapi Evgeniy Polyakov
2007-05-22 15:19 ` Sebastian Siewior
2007-05-23 8:03 ` Evgeniy Polyakov [this message]
2007-05-23 10:02 ` Sebastian Siewior
2007-05-23 12:30 ` Evgeniy Polyakov
2007-05-25 8:31 ` Herbert Xu
2007-05-25 8:21 ` Herbert Xu
2007-05-25 9:00 ` Evgeniy Polyakov
2007-05-25 11:03 ` Herbert Xu
2007-05-25 8:14 ` Herbert Xu
2007-05-25 8:55 ` Evgeniy Polyakov
2007-05-25 9:35 ` Sebastian Siewior
2007-05-25 10:20 ` Evgeniy Polyakov
2007-05-25 11:35 ` Herbert Xu
2007-05-25 11:01 ` Herbert Xu
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=20070523080354.GA19665@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=linux-crypto@ml.breakpoint.cc \
--cc=linux-crypto@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