netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Samuel Tardieu <sam@rfc1149.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org
Subject: Re: [ACRYPTO] New asynchronous crypto layer (acrypto) release.
Date: Fri, 29 Sep 2006 14:51:20 +0400	[thread overview]
Message-ID: <20060929105118.GA20194@2ka.mipt.ru> (raw)
In-Reply-To: <87wt7nm0x5.fsf@willow.rfc1149.net>

On Fri, Sep 29, 2006 at 12:17:58PM +0200, Samuel Tardieu (sam@rfc1149.net) wrote:
> >>>>> "Evgeniy" == Evgeniy Polyakov <johnpol@2ka.mipt.ru> writes:
> 
> 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?

Userspace supports Via Nehemiah CPUs crypto engine quite for a long time
without any external patching.

>   Sam
> -- 
> Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/

-- 
	Evgeniy Polyakov

      reply	other threads:[~2006-09-29 10:51 UTC|newest]

Thread overview: 6+ 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
     [not found] ` <451BCCDF.5000201@ciphirelabs.com>
2006-09-29  9:48   ` Evgeniy Polyakov
2006-09-29 10:17 ` Samuel Tardieu
2006-09-29 10:51   ` Evgeniy Polyakov [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=20060929105118.GA20194@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).