Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: linux-crypto@vger.kernel.org
Subject: Re: Asynchronus crypto API
Date: Wed, 21 Feb 2007 12:27:33 -0500	[thread overview]
Message-ID: <erhvfe$uun$1@sea.gmane.org> (raw)
In-Reply-To: <20070209113108.GA11467@2ka.mipt.ru>

Evgeniy Polyakov wrote:
> 2. ocf
> http://ocf-linux.sourceforge.net/

Please note that much more recent code is now at:
    git clone http://hifn.xelerance.com/scm/klips/

There is one remaining bug that has been hard to reproduce which
seems to be at the IPsec layer, but the OCF and hardware drivers
are very stable.  For software crypto, it uses cryptoapi, and can
invoke them asynchronously if you like.
The code does not apply to >=2.6.19 due the recent changes, and we
will catch it up to the new cryptoapi interface in the next week
or so.

  parent reply	other threads:[~2007-02-26 16:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 11:08 Asynchronus crypto API Joerg Roedel
2007-02-09 11:31 ` Evgeniy Polyakov
2007-02-09 12:16   ` Joerg Roedel
2007-02-09 12:31     ` Evgeniy Polyakov
2007-02-21 17:27   ` Michael Richardson [this message]
2007-02-13 22:14 ` 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='erhvfe$uun$1@sea.gmane.org' \
    --to=mcr@sandelman.ca \
    --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