All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Jardin <vincent.jardin@6wind.com>
To: Samuel Tardieu <sam@rfc1149.net>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [ACRYPTO] New asynchronous crypto layer (acrypto) release.
Date: Fri, 29 Sep 2006 19:31:28 +0200	[thread overview]
Message-ID: <451D5870.6020100@6wind.com> (raw)
In-Reply-To: <87wt7nm0x5.fsf@willow.rfc1149.net>

For the best synergy with OpenBSD guys, the OCF API should be considered:
   
http://www.usenix.org/events/usenix03/tech/full_papers/keromytis/keromytis_html/node8.html

then, whatever a HW driver is added, the same IOCTLs will be used by 
OpenSSL. The OCF patch for OpenSSL is already available.

Currently, it is not into the kernel git's repository so I think that 
your Via CPU won't get better performances with OpenSSL

Regards,
   Vincent

Samuel Tardieu wrote:

>Evgeniy> Hello.  I'm pleased to announce asynchronous crypto layer
>Evgeniy> (acrypto) [1] release for 2.6.18 kernel tree. Acrypto allows
>Evgeniy> to handle crypto requests asynchronously in hardware.
>
>Would userspace programs benefit from this patch? In particular, would
>OpenSSL get better performances on Via nehemiah CPUs or does it need
>to be patched?
>
>  Sam
>  
>


      parent reply	other threads:[~2006-09-29 17:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-28 12:08 [ACRYPTO] New asynchronous crypto layer (acrypto) release Evgeniy Polyakov
2006-09-28 13:23 ` Andreas Jellinghaus
2006-09-28 13:23 ` Andreas Jellinghaus
2006-09-28 13:23 ` Andreas Jellinghaus
2006-09-28 13:23   ` Andreas Jellinghaus
2006-09-28 13:35   ` Evgeniy Polyakov
2006-09-29  9:48   ` Evgeniy Polyakov
2006-10-19 15:04     ` Andreas Jellinghaus
2006-10-20  6:31       ` Evgeniy Polyakov
2006-10-20 13:34         ` Andreas Jellinghaus
2006-10-21  6:59           ` Evgeniy Polyakov
2006-09-29 10:17 ` Samuel Tardieu
2006-09-29 10:51   ` Evgeniy Polyakov
2006-09-29 17:31   ` Vincent Jardin [this message]

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=451D5870.6020100@6wind.com \
    --to=vincent.jardin@6wind.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=sam@rfc1149.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.