Bug#886150: [Pkg-dpdk-devel] Bug#886150: Please enable OpenSSL crypto driver
Hello, 2018-02-08 18:38 GMT+03:00 Luca Boccassi : > Thank you very much for providing test commands and checking the 1.0 > support. > > We'll be uploading DPDK 18.02 to Debian experimental shortly after it > will release in a few days, and it will have the OpenSSL PMD enabled > there, so that it can be tested for a while. > > Then, after Ubuntu 18.04 freezes and stops importing from unstable (too > late to add such new features now), we can enable it in sid and testing > as well. > > Hope this sounds like a good plan for you. Yes, this sounds good enough. In the mean time I will be able to test our software against DPDK from experimental. -- With best wishes Dmitry
Bug#886150: [Pkg-dpdk-devel] Bug#886150: Please enable OpenSSL crypto driver
Control: tags -1 pending On Wed, 31 Jan 2018 02:20:11 +0300 Dmitry Eremin-Solenikov wrote: > 2018-01-31 1:43 GMT+03:00 Dmitry Eremin-Solenikov : > > Hello, > > > > 2018-01-04 18:22 GMT+03:00 Christian Ehrhardt > > : > >> On Tue, Jan 2, 2018 at 6:26 PM, Dmitry Eremin-Solenikov > >> wrote: > >>> Source: dpdk > >>> Version: 17.11-3 > >>> Severity: wishlist > >>> > >>> Hello, > >>> > >>> Could you please enable CONFIG_RTE_LIBRTE_PMD_OPENSSL (Software backed > >>> crypto driver). It will make it possible to use DPDK crypto > >>> transformations without actual hardware support). > >> > >> there are certain constraints applying. > >> > >> 1. none of the DEB_DPDK maintainers has used this so it would be great > >> if you could provide a set of testcases to ensure things work. > > > > Hmm. I think usual crypto test cases should work. > > Following commands should work with crypto_openssl: > > dpdk-test-crypto-perf --vdev crypto_openssl -- --devtype > crypto_openssl --digest-sz 20 > > dpdk-test-crypto-perf --vdev crypto_openssl -- --devtype > crypto_openssl --optype aead --aead-algo aes-gcm --aead-key-sz 16 > --aead-iv-sz 12 --digest-sz 16 > > >> 2. furthermore we learned (the hard way) that enabling non default > >> enabled drivers break us often. > >> This is due to them being exposed to way less testing and verification. > > > > OpenSSL PMD driver is regularly used on our project (ODP). It is supported > > by upstream, we never had any issues. > > > >> 3. Also we here have the special case that if possible it has to work > >> with openssl 1.0 (Ubuntu) AND 1.1 (Debian) > >> According to the docs currently it does only the former. > > DPDK 17.11 properly support OpenSSL 1.0. Verified that by building it > from source and testing. > > -- > With best wishes > Dmitry Hello Dmitry, Thank you very much for providing test commands and checking the 1.0 support. We'll be uploading DPDK 18.02 to Debian experimental shortly after it will release in a few days, and it will have the OpenSSL PMD enabled there, so that it can be tested for a while. Then, after Ubuntu 18.04 freezes and stops importing from unstable (too late to add such new features now), we can enable it in sid and testing as well. Hope this sounds like a good plan for you. -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#886150: [Pkg-dpdk-devel] Bug#886150: Please enable OpenSSL crypto driver
2018-01-31 1:43 GMT+03:00 Dmitry Eremin-Solenikov : > Hello, > > 2018-01-04 18:22 GMT+03:00 Christian Ehrhardt > : >> On Tue, Jan 2, 2018 at 6:26 PM, Dmitry Eremin-Solenikov >> wrote: >>> Source: dpdk >>> Version: 17.11-3 >>> Severity: wishlist >>> >>> Hello, >>> >>> Could you please enable CONFIG_RTE_LIBRTE_PMD_OPENSSL (Software backed >>> crypto driver). It will make it possible to use DPDK crypto >>> transformations without actual hardware support). >> >> there are certain constraints applying. >> >> 1. none of the DEB_DPDK maintainers has used this so it would be great >> if you could provide a set of testcases to ensure things work. > > Hmm. I think usual crypto test cases should work. Following commands should work with crypto_openssl: dpdk-test-crypto-perf --vdev crypto_openssl -- --devtype crypto_openssl --digest-sz 20 dpdk-test-crypto-perf --vdev crypto_openssl -- --devtype crypto_openssl --optype aead --aead-algo aes-gcm --aead-key-sz 16 --aead-iv-sz 12 --digest-sz 16 >> 2. furthermore we learned (the hard way) that enabling non default >> enabled drivers break us often. >> This is due to them being exposed to way less testing and verification. > > OpenSSL PMD driver is regularly used on our project (ODP). It is supported > by upstream, we never had any issues. > >> 3. Also we here have the special case that if possible it has to work >> with openssl 1.0 (Ubuntu) AND 1.1 (Debian) >> According to the docs currently it does only the former. DPDK 17.11 properly support OpenSSL 1.0. Verified that by building it from source and testing. -- With best wishes Dmitry
Bug#886150: [Pkg-dpdk-devel] Bug#886150: Please enable OpenSSL crypto driver
Hello, 2018-01-04 18:22 GMT+03:00 Christian Ehrhardt : > On Tue, Jan 2, 2018 at 6:26 PM, Dmitry Eremin-Solenikov > wrote: >> Source: dpdk >> Version: 17.11-3 >> Severity: wishlist >> >> Hello, >> >> Could you please enable CONFIG_RTE_LIBRTE_PMD_OPENSSL (Software backed >> crypto driver). It will make it possible to use DPDK crypto >> transformations without actual hardware support). > > there are certain constraints applying. > > 1. none of the DEB_DPDK maintainers has used this so it would be great > if you could provide a set of testcases to ensure things work. Hmm. I think usual crypto test cases should work. > 2. furthermore we learned (the hard way) that enabling non default > enabled drivers break us often. > This is due to them being exposed to way less testing and verification. OpenSSL PMD driver is regularly used on our project (ODP). It is supported by upstream, we never had any issues. > 3. Also we here have the special case that if possible it has to work > with openssl 1.0 (Ubuntu) AND 1.1 (Debian) > According to the docs currently it does only the former. I will try patching latest DPDK to support SSL 1.0. Does Ubuntu have any timeline for migrating to SSL 1.1. -- With best wishes Dmitry
Bug#886150: [Pkg-dpdk-devel] Bug#886150: Please enable OpenSSL crypto driver
On Tue, Jan 2, 2018 at 6:26 PM, Dmitry Eremin-Solenikov wrote: > Source: dpdk > Version: 17.11-3 > Severity: wishlist > > Hello, > > Could you please enable CONFIG_RTE_LIBRTE_PMD_OPENSSL (Software backed > crypto driver). It will make it possible to use DPDK crypto > transformations without actual hardware support). Hi Dmitry, there are certain constraints applying. 1. none of the DEB_DPDK maintainers has used this so it would be great if you could provide a set of testcases to ensure things work. 2. furthermore we learned (the hard way) that enabling non default enabled drivers break us often. This is due to them being exposed to way less testing and verification. 3. Also we here have the special case that if possible it has to work with openssl 1.0 (Ubuntu) AND 1.1 (Debian) According to the docs currently it does only the former. We can work on all of that, but at a slow pace. You could request at DPDK upstream if they consider it stable enough to be default enabled? And you might also mention the multi-openssl version compatibility to be a nice to have. > -- > With best wishes > Dmitry > > > -- System Information: > Debian Release: buster/sid > APT prefers testing > APT policy: (500, 'testing') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores) > Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), > LANGUAGE=en_GB:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > ___ > Pkg-dpdk-devel mailing list > pkg-dpdk-de...@lists.alioth.debian.org > https://lists.alioth.debian.org/mailman/listinfo/pkg-dpdk-devel -- Christian Ehrhardt Software Engineer, Ubuntu Server Canonical Ltd