Sergio, thx for following up. Are VPP packages with Cryptodev built today as
part of any of the vpp verify jobs? Cause they should be, and depositing them
in nexus on merge into master should be the default IMV. If so, CSIT will just
take these from nexus.
vpp-dev, could anybody advise here further?
-Maciek
> On 4 Jan 2017, at 16:53, Sergio Gonzalez Monroy
> <sergio.gonzalez.mon...@intel.com> wrote:
>
> Hi,
>
> We were discussing on the CSIT project weekly call the required setup for
> testing VPP with DPDK Cryptodev.
>
> As it was agreed on VPP call, DPDK Cryptodev support in VPP is disabled by
> default and needs to be manually enabled.
> Basically, when we build VPP with DPDK Cryptodev support
> ('vpp_uses_dpdk_cryptodev=yes' at build time) we enable some Cryptodev PMDs
> that are disabled in DPDK by default.
> At the moment, the following Crypto PMDs are built:
> - QAT PMD: Driver for Intel QuickAssist Technology (QAT) devices.
> - AESNI-MB PMD: Software crypto with dependency on 'Intel IPsec Multibuffer
> library'
> - AESNI-GCM PMD: Software crypto with dependency on 'Intel IPsec Multibuffer
> library'
>
> The latest 'Intel IPsec Multibuffer' library source code is located in:
> https://github.com/01org/intel-ipsec-mb.git
>
> To successfully build DPDK with those PMDs enabled, we previously need to
> build the 'Intel IPsec Multibuffer library' and set up the env variable
> AESNI_MULTI_BUFFER_LIB_PATH.
>
> From the call, it looks like we need (please correct me as I am likely to be
> wrong given my CSIT knowledge):
> - VPP package built with Cryptodev support in Nexus
> - Something else for verify job? (can someone add details here please?)
>
>
> Thanks,
> Sergio
> _______________________________________________
> csit-dev mailing list
> csit-...@lists.fd.io
> https://lists.fd.io/mailman/listinfo/csit-dev
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
