All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Thara Gopinath <thara.gopinath@linaro.org>,
	Eric Biggers <ebiggers@kernel.org>
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: Qualcomm Crypto Engine performance numbers on mainline kernel
Date: Sat, 5 Jun 2021 17:32:59 +0200	[thread overview]
Message-ID: <CAMj1kXGRb=_tozRAMA+ZFbAHU4P7ocLbWq+B3s0ngoRoo82V6g@mail.gmail.com> (raw)
In-Reply-To: <bc3c139f-4c0c-a9b7-ae00-59c2f8292ef8@linaro.org>

Hello Thara,

On Fri, 4 Jun 2021 at 18:49, Thara Gopinath <thara.gopinath@linaro.org> wrote:
>
>
> Hi All,
>
> Below are the performance numbers from running "crypsetup benchmark" on
> CE algorithms in the mainline kernel. All numbers are in MiB/s. The
> platform used is RB3 for sdm845 and MTPs for rest of them.
>
>
>                         SDM845    SM8150     SM8250     SM8350
> AES-CBC (128)
> Encrypt / Decrypt       114/106  36/48       120/188    133/197
>
> AES-XTS (256)
> Encrypt / Decrypt       100/102  49/48       186/187    n/a
>

The CPU instruction based ones are apparently an order of magnitude
faster, and are synchronous so their latency should be lower.

So, as Eric already pointed out IIRC, there doesn't seem to be much
value in enabling this IP in Linux - it should not be the default
choice/highest priority, and it is not obvious to me whether/when you
would prefer this implementation over the CPU based one. Do you have
any idea how many queues it has, or how much data it can process in
parallel? Are there other features that stand out?

  reply	other threads:[~2021-06-05 15:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 16:49 Qualcomm Crypto Engine performance numbers on mainline kernel Thara Gopinath
2021-06-05 15:32 ` Ard Biesheuvel [this message]
2021-06-06  6:49   ` Gilad Ben-Yossef
2021-06-06 10:07   ` Christian Lamparter

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='CAMj1kXGRb=_tozRAMA+ZFbAHU4P7ocLbWq+B3s0ngoRoo82V6g@mail.gmail.com' \
    --to=ardb@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=thara.gopinath@linaro.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 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.