From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Date: Mon, 3 Jul 2017 09:29:59 +0200 From: Alexander Dahl Message-ID: <20170703072958.GR27745@falbala.home.lespocky.de> References: <20170624134751.gfpub6mrshdwz6cd@lenoch> <20170630143621.pvtqwd44u7k4xunz@pengutronix.de> <20170630192504.jyhzavla2htlupmg@lenoch> <20170702203030.GB26018@archie.localdomain> <20170702220326.GP27745@falbala.home.lespocky.de> <20170703065642.f33blay7w7ttxe6x@pengutronix.de> MIME-Version: 1.0 In-Reply-To: <20170703065642.f33blay7w7ttxe6x@pengutronix.de> Subject: Re: [ptxdist] [RFC/PATCH 0/3] cryptodev List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: multipart/mixed; boundary="===============0526735621==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de Cc: Robert Schwebel , fli4l-dev@eisler.nettworks.org --===============0526735621== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1bhFRg6vL9BT9osV" Content-Disposition: inline --1bhFRg6vL9BT9osV Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hei hei, cross post following =E2=80=A6 ;-) 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? > >=20 > > 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. >=20 > 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=20 (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 --=20 =C2=BBWith the first link, the chain is forged. The first speech censured,= =20 the first thought forbidden, the first freedom denied, chains us all=20 irrevocably.=C2=AB (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: C28E E6B9 0263 95CF 8FAF 08FA 34AD CD00 7221 5CC6 *** --1bhFRg6vL9BT9osV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABCAAGBQJZWfJ1AAoJEDStzQByIVzGsGUP/22mlz6YxcTf0siGddUHtqvG rXGs7ixPfTyI6acfP6hqtAHCtS90oe2n+Yw/kCLZMGKzXAHp6P2TgrWC+aqDZZpH RSXxMNCcNqtEeF+HQ6bpikaDMgRl6otPExDOfeeavxnBPK+zD3N97dQ8iKa+jeoj PJ28W1+poMlp6XJ56sWJs4r9uktm6Xyhh1MXizYUTZ4CcDm8db4OsUaj+difebUg NOGRfZ1oKEBDiNJk+3866QoumAikQWtbE2geSsmunUDbDxyVqMw6Wd1i/oYlVnOu aEHXjmgFTIemo/2ByZzRW3gO9PA5Kx9Oc5gFnqBo6kNTZh8VrJYEczwxJQ3lBwso IV4IZx9YnxyaWD3WuK/POGpC2/Z217VasLy/z6kKJya05KHka7AEvf++U3DHuLJk sjm98YVmSTF0LZj5gNhayrGyO+yBWys71VfZNNWxz1QeOcYUbFdU08A63PFu1SzZ sPaKI98MFi5G7Em/jV3pglgUGwoXv7ZRzmK9Ja9fwKySbJLayw0eVzoT8XDmbXnp 1T6E+iPraNj+yrM7E6mLQQV9GdUwNjs5TBarmjmD1v3a84hajBj+UPd8tDFqGUBq 2/6RKu46FRU844CyG1wijSV74v1myZcNlqpsAqnRBz1qGQIYn+CHqfLbcNpHBNiU ECq3DIqpzqFcVGEgyTvY =N5fI -----END PGP SIGNATURE----- --1bhFRg6vL9BT9osV-- --===============0526735621== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============0526735621==--