> On Mon, 26 May 2025 at 14:15, Akhil Goyal <gak...@marvell.com> wrote: > > > > > DPDK deprecation notice need not include API changes in external libraries. > > We just need to notify the users about the version of ZSDA external lib is > > going > to change in next release or so. > > And then we can change the code. > > > > You can refer to intel-ipsec-mb. It manages compatible external library > > version > in dpdk docs. > > > > Thanks Akhil > > Will add this. > I am waiting for the 2.9 release, which may happen this weekend. > > diff --git a/doc/guides/rel_notes/release_25_07.rst > b/doc/guides/rel_notes/release_25_07.rst > index 0c9ec76355..138bfecd61 100644 > --- a/doc/guides/rel_notes/release_25_07.rst > +++ b/doc/guides/rel_notes/release_25_07.rst > @@ -72,6 +72,11 @@ New Features > > * Support matching on IPv6 frag extension header with async flow > template API. > > +* **Updated UADK crypto & compress driver.** > + > + * Update to init2 interface which requires v2.9 of the UADK library. > + * Update to asynchronous mode for better performance. > + > * **Updated virtio driver.** > > Is this suitable to squash into the last patch together? > Yes, but you need to update your driver documentation also. You may maintain a table to specify which dpdk version is compatible with which uadk lib
Check doc/guides/cryptodevs/aesni_mb.rst for reference.
