From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC/PATCH 0/3] cryptodev
Date: Mon, 17 Jul 2017 10:56:20 +0200 [thread overview]
Message-ID: <20170717085620.agywx4x26od6upng@pengutronix.de> (raw)
In-Reply-To: <20170710141120.6stgminsubmgxbje@lenoch>
On Mon, Jul 10, 2017 at 04:11:20PM +0200, Ladislav Michl wrote:
> 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?
>
> The module itself is 10+ years old and it is highly unlikely it will be
> ever merged as it uses ioctl approach - makes API compatible with OpenBSD.
> Meawhile AF_ALG API was introduced without anyone really interested (people
> are still using /dev/crypto). Also see this comparsion:
> http://cryptodev-linux.org/comparison.html
I'm not concerned about upstream, but keeping it up to date in PTXdist.
As long as it's not in the mainline kernel, we have a separate packages
that needs to be maintained.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-07-17 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 [this message]
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=20170717085620.agywx4x26od6upng@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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