mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC/PATCH 0/3] cryptodev
Date: Sun, 2 Jul 2017 22:30:30 +0200	[thread overview]
Message-ID: <20170702203030.GB26018@archie.localdomain> (raw)
In-Reply-To: <20170630192504.jyhzavla2htlupmg@lenoch>

Hi,

On Fri, Jun 30, 2017 at 09:25:04PM +0200, Ladislav Michl wrote:
> On Fri, Jun 30, 2017 at 04:36:21PM +0200, Michael Olbrich wrote:
> > Hi,
> > 
> > On Sat, Jun 24, 2017 at 03:47:51PM +0200, Ladislav Michl wrote:
> > > This serie adds support for cryptodev hardware acceleration.
> > > However, there's one issue unresolved: cryptodev module
> > > loading.
> > > As we have three different modutils implementations available
> > > and also supporting systemd and sysv init it is a bit messy
> > > to generate proper config to load cryptodev at boot time.
> > > So we could either leave module loading to BSP or do something
> > > on ptxdist level. Thoughts?
> > 
> > I'm not sure I like this. Keeping up to date with crypto stuff is hard
> > enough as it is. I don't like adding a out-of-tree kernel module into the
> > mix.
> 
> Fair enough, but note this module is there for long time and still properly
> maintained.

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?

Thanks,
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2017-07-02 20:30 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 [this message]
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

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=20170702203030.GB26018@archie.localdomain \
    --to=clemens.gruber@pqgruber.com \
    --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