Re: engine_pkcs11: performance - offer to sponsorship

Timo Teras <[email protected]> Sun, 7 Feb 2021 10:38:19 +0200
Newsgroups gmane.comp.encryption.opensc.devel
Message-ID <[email protected]>
--===============7771029789361833180==
Content-Type: multipart/signed; boundary="Sig_/1ciiWGLDJRyyQNSiMnnq=1L";
 protocol="application/pgp-signature"; micalg=pgp-sha256

--Sig_/1ciiWGLDJRyyQNSiMnnq=1L
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

Do you have more detailed project description available yet? What kind
of time schedule expectation you have?

Also, what I hear as underlying change to use more sessions and cache
them, might require quite big redesign of libp11. And it might be
easier to rewrite. Would this be an option if analysis suggests this is
better approach?

Timo

On Fri, 5 Feb 2021 16:00:15 +0100
Ond=C5=99ej Sur=C3=BD <[email protected]> wrote:

> Hi OpenSC folks,
>=20
> Internet Systems Corporation, Inc. maker of BIND 9 is looking for a
> short-term contractor that would work on engine_pkcs11 performance.
>=20
> The friendly support staff of Ultra-CIS, the maker of AEP Keeper came
> up with following observation when comparing engine_pkcs11 to the old
> Solaris/Oracle OpenSSL patch:
>=20
> > 	=E2=80=A2 OpenSC libp11 Engine performs 13 more C_FindObjects calls
> > 	=E2=80=A2 OpenSC libp11 Engine performs 50 more C_GetAttributeValue
> > calls
> > 	=E2=80=A2 OpenSC libp11 Engine performs 1986 more C_SignInit calls
> > 	=E2=80=A2 OpenSC libp11 Engine performs 2174 more C_Sign calls
> > 	=E2=80=A2 OpenSSL patched version uses 17 sessions and OpenSC
> > libp11 Engine only uses 1
> > 	=E2=80=A2 OpenSC libp11 Engine appears not to close it=E2=80=99s sessi=
on.
> >=20
> > I think the most significant thing here is that OpenSC libp11
> > Engine only uses one session, whereas OpenSSL patched version uses
> > 17. Using multiple sessions can increase throughput and I suspect
> > this is the reason why OpenSSL patched version has a better
> > performance. =20
>=20
> ISC would be willing to sponsor further development of engine_pkcs11
> under the same license as the original code and contributed back to
> OpenSC project. Further details could be discussed with me, but we
> are generally looking at work that would be of benefit to the BIND 9
> users, but also to the whole OpenSC community.
>=20
> You can contact me on this email or same username at isc.org.
>=20
> Cheers,
> Ondrej
> --
> Ond=C5=99ej Sur=C3=BD (He/Him)
> [email protected]
>=20


--Sig_/1ciiWGLDJRyyQNSiMnnq=1L
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE4I3Qw8xW2vccyUOwGUPPIx6Caf8FAmAfpvsACgkQGUPPIx6C
af8CWQ//XCflVyiVcWdOd0Tz7vPHsw2hXWfurGBJ8hViofUTyuXI0YTfvLyZYzLt
vDEbwQRT8IiszfG0+9y14UCra9AH4gI8gHesEAufUbm85N4RoqRjUBOz5rN8RhDL
pJfZGucMXBhU1wVDDvrH51Ru29glksWG4nEHi68O7Fyrgcg6WsDCqhuxRVEIIPqy
+yF4+F5MjDTjC0nuiyXpCrVbYrzEXjt44tEINdMu++vrzPbw8XQWzdaUhgP0/onq
QAXVOrrd0E4NAn+YhORiMuwwRx0cgn7KqY8ZD0dyGkkDOdtPOZVBqJoMLqFVZ8AQ
Lc5LrezxhnC3db09oz/Bq/qW6pIrsgU25hRhYEe58rtbyyJejJxJv131itdoSo/l
s3WdErmuNQtQb3Of+wQtgrW+Yu0GY4jyG3cnl4k6jiuSUJCAt3L03PaB6FKYGnn8
Oflsx4EQvktHYYSzrJmhez1Sd9+EvRd8czaMZ25gsu3fXCcKy/ZIwt1j2JiRc1wp
BSl32g8FyUbh7l4RnhwNKJFmGZmQGTQkuchnY4IekVn42E1l+9mDwsEjEHsXERnG
NgfZxuNQoNxRkcxljzDSc1iiIktjmYB73h6XvK/teLeeIX3L1EnJ90JpgarIzjd8
b1ieECTV1GvtXo/UGi4/OgovJFofGbb6kF2pznGJ3H9c6pP2wTU=
=g/tU
-----END PGP SIGNATURE-----

--Sig_/1ciiWGLDJRyyQNSiMnnq=1L--


--===============7771029789361833180==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============7771029789361833180==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Opensc-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensc-devel

--===============7771029789361833180==--