From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC/PATCH 0/3] cryptodev
Date: Tue, 11 Jul 2017 10:56:11 +0200 [thread overview]
Message-ID: <20170711085611.odja32mcot7q6uxm@lenoch> (raw)
In-Reply-To: <20170702203030.GB26018@archie.localdomain>
On Sun, Jul 02, 2017 at 10:30:30PM +0200, Clemens Gruber wrote:
> I am wondering about the performance improvements when using the
> cryptodev openssl engine. There must be some cost for the context
> switches, but this is probably outweighed by the offloading.
> Did you for example run openssl speed aes-128-cbc before and after?
> And on what platform did you try it?
The cost of the context switches is notable only for small payloads,
bigger payload makes hw acceleration more usefull. Bellow is openssl
speed test result as run on IGEPv2 board with DM3730 (OMAP3630) -
second line is using cryptodev engine
(omap-aes 480c5000.aes: OMAP AES hw accel rev: 2.6):
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
aes-128-cbc 25210.41k 32946.13k 35359.47k 36149.68k 36203.09k
aes-128-cbc 8821.87k 55293.26k 34594.13k 308582.40k infk
ladis
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2017-07-11 8:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 13:47 Ladislav Michl
2017-06-24 13:48 ` [ptxdist] [PATCH 1/3] cryptodev: new package Ladislav Michl
2017-06-24 13:49 ` [ptxdist] [PATCH 2/3] openssl: add cryptodev support Ladislav Michl
2017-06-24 13:49 ` [ptxdist] [PATCH 3/3] gnutls: " Ladislav Michl
2017-06-30 14:36 ` [ptxdist] [RFC/PATCH 0/3] cryptodev Michael Olbrich
2017-06-30 19:25 ` Ladislav Michl
2017-07-02 20:30 ` Clemens Gruber
2017-07-02 22:03 ` Alexander Dahl
2017-07-03 6:56 ` Robert Schwebel
2017-07-03 7:29 ` Alexander Dahl
2017-07-10 14:11 ` Ladislav Michl
2017-07-17 8:56 ` Michael Olbrich
2017-07-11 8:56 ` Ladislav Michl [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=20170711085611.odja32mcot7q6uxm@lenoch \
--to=ladis@linux-mips.org \
--cc=ptxdist@pengutronix.de \
/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