From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Cc: Robert Schwebel <r.schwebel@pengutronix.de>,
fli4l-dev@eisler.nettworks.org
Subject: Re: [ptxdist] [RFC/PATCH 0/3] cryptodev
Date: Mon, 3 Jul 2017 09:29:59 +0200 [thread overview]
Message-ID: <20170703072958.GR27745@falbala.home.lespocky.de> (raw)
In-Reply-To: <20170703065642.f33blay7w7ttxe6x@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1759 bytes --]
Hei hei,
cross post following … ;-)
On Mon, Jul 03, 2017 at 08:56:42AM +0200, Robert Schwebel wrote:
> On Mon, Jul 03, 2017 at 12:03:26AM +0200, Alexander Dahl wrote:
> > 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?
> >
> > fli4l [1] uses cryptodev and the experience there is, it depends on
> > the platform. Some platforms benefit a lot, especially for OpenVPN,
> > others not so much. Depends on what the CPU offers and how fast the
> > system in general is.
>
> Do you know why the module is not in mainline? Is there a discussion
> where the kernel maintainers motivate why they don't like this solution?
Sorry, I do not know. IIRC did we switch from some other hardware
acceleration approach in fli4l some time ago, but I can't remember any
details, and I doubt your question was discussed within the fli4l
team. The ticket in the fli4l bugtracker is this one:
https://ssl.nettworks.org/bugs/browse/FFL-946
(You may notice it's a German project ;-) ).
I forward this conversation to the (not yet open) fli4l developer
list, maybe Christoph Schulz has more insights?
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF 08FA 34AD CD00 7221 5CC6 ***
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-07-03 7:29 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 [this message]
2017-07-10 14:11 ` Ladislav Michl
2017-07-17 8:56 ` Michael Olbrich
2017-07-11 8:56 ` Ladislav Michl
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=20170703072958.GR27745@falbala.home.lespocky.de \
--to=post@lespocky.de \
--cc=fli4l-dev@eisler.nettworks.org \
--cc=ptxdist@pengutronix.de \
--cc=r.schwebel@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