Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [0/6] [CRYPTO]: Async blkcipher backend support
Date: Mon, 16 Apr 2007 15:28:42 +0400	[thread overview]
Message-ID: <20070416112842.GA2207@2ka.mipt.ru> (raw)
In-Reply-To: <20070416105105.GA10188@gondor.apana.org.au>

On Mon, Apr 16, 2007 at 08:51:05PM +1000, Herbert Xu (herbert@gondor.apana.org.au) wrote:
> Hi:
> 
> This series of patches adds the backend support for asynchronous blkcipher
> implementations.  This includes the ablkcipher crypto type, generic crypto
> request queueing, as well as a sample cryptd implementation that turns any
> sync blkcipher algorithm into an async one by processing requests in a
> dedicated kernel thread.
> 
> This allows drivers for hardware blkcipher devices to be written.

Hi Herbert.

Good to see async crypto processing is being (a bit slowly - more than a
year after we talked about it previously :) completed.
With this patchset included there will not be requirement for another async levels,
so I can port HIFN 795x driver from acrypto to this one.

Do you have a stable git tree to pull from, so I could prepare a testbed.
(althugh I can not start right now, but expect to do it soon).

And, hmm, your documentation really sucks, could you write a draft for
async api and put it into the tree?

Thanks for the work.

-- 
	Evgeniy Polyakov

  reply	other threads:[~2007-04-16 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-16 10:51 [0/6] [CRYPTO]: Async blkcipher backend support Herbert Xu
2007-04-16 11:28 ` Evgeniy Polyakov [this message]
2007-04-16 12:39   ` 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=20070416112842.GA2207@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=herbert@gondor.apana.org.au \
    --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