linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Conor O'Gorman <i@conorogorman.net>
To: linuxppc-dev@ozlabs.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v1 0/3] SHA256 for PPC/SPE
Date: Fri, 30 Jan 2015 12:02:42 +0000	[thread overview]
Message-ID: <54CB72E2.1030101@conorogorman.net> (raw)
In-Reply-To: <5ad377b3-e491-4c35-8b89-de1dfd0749a6__44574.29146064$1422133918$gmane$org@EXCHANGE.collogia.de>

On 24/01/15 21:10, Markus Stockhausen wrote:
> [PATCH v1 0/3] SHA256 for PPC/SPE
>
> The following patches add support for SIMD accelerated SHA256
> calculation on PPC processors with SPE instruction set. The

Nice boost.

Many of the SoCs with e500 core have crypto hardware accelerators. How 
does this compare?

Thanks,
Conor

       reply	other threads:[~2015-01-30 12:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5ad377b3-e491-4c35-8b89-de1dfd0749a6__44574.29146064$1422133918$gmane$org@EXCHANGE.collogia.de>
2015-01-30 12:02 ` Conor O'Gorman [this message]
2015-01-30 13:41   ` AW: [PATCH v1 0/3] SHA256 for PPC/SPE Markus Stockhausen
2015-01-24 21:10 Markus Stockhausen
2015-01-26  0:18 ` Herbert Xu
2015-01-26  5:19   ` Markus Stockhausen

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=54CB72E2.1030101@conorogorman.net \
    --to=i@conorogorman.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).