On Wed, Feb 21, 2024 at 4:50 AM Power, Ciara <ciara.po...@intel.com> wrote:
> > Hi folks, > > We had based the ipsec-mb version bump to 1.4 on both intel ipsec-mb and > arm ipsec-mb supporting that version, so both could still use the Ipsec-mb > SW PMDs. > I based the arm support from the repo main branch ( > https://gitlab.arm.com/arm-reference-solutions/ipsec-mb/-/tree/main) > It's version is 1.4 and looks like some of the code changes from > intel-ipsec-mb 1.4 have been merged in (e.g. imb_set_session function which > is 1.4+). > I know there was issues before with it being tagged as 1.4 too soon - is > that still the case, or is the main branch up to date now with > intel-ipsec-mb 1.4? > > Thanks, > Ciara > Hi Ciara, I see what you mean and did a test on an arm container. I used tip of main for ipsec-mb, applied the v1.4 requirement patch to dpdk, built dpdk and was able to run the ZUC autotest with the zuc vdev pmd. root@8aad8acde315:/opt/dpdk/build# meson test cryptodev_sw_zuc_autotest --test-args="--no-huge --no-pci --vdev=crypto_zuc" ninja: no work to do. ninja: Entering directory `/opt/dpdk/build' ninja: no work to do. 1/1 DPDK:driver-tests / cryptodev_sw_zuc_autotest OK 0.22s Ok: 1 Expected Fail: 0 Fail: 0 Unexpected Pass: 0 Skipped: 0 Timeout: 0 Usually when we install dependencies we go from a tag which is stable. We'll update the dpdk-ci container image template engine to clone the repo and then checkout to this commit which is known to be good: cef9b8924e3ff52f2c5a3703860008c27ee723c4. And our automated testing can remain online in this way. Arm folks, I'm not sure what your plans are but at some point in the docs I think pages like: https://doc.dpdk.org/guides/cryptodevs/zuc.html https://doc.dpdk.org/guides/cryptodevs/snow3g.html should be updated to reference this commit, or a newly introduced tag, to reflect that the SECLIB-IPSEC-2023.06.20 tag will no longer work for 24.03 as it is ipsec 1.3. Thanks for the help.
