From: Zhangfei Gao <zhangfei.gao@linaro.org>
To: Akhil Goyal <gakhil@marvell.com>
Cc: "Marchand, David" <david.marchand@redhat.com>,
Aaron Conole <aconole@redhat.com>,
Fan Zhang <fanzhang.oss@gmail.com>,
Ashish Gupta <ashishg@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Subject: Re: [EXTERNAL] [PATCH 0/2] uadk: realize async mode
Date: Mon, 16 Jun 2025 10:56:48 +0800 [thread overview]
Message-ID: <CABQgh9EXg94dopaqD-ReF51V699GZyiO7f3PzFbvK0AVsB3aQQ@mail.gmail.com> (raw)
In-Reply-To: <CO6PR18MB4484BB354A2EE063C647F89CD86CA@CO6PR18MB4484.namprd18.prod.outlook.com>
On Wed, 4 Jun 2025 at 23:29, Akhil Goyal <gakhil@marvell.com> wrote:
>
>
> > On Mon, 26 May 2025 at 14:15, Akhil Goyal <gakhil@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
I just sent v2, which depends on UADK 2.9 release.
I am waiting for the 2.9 release for two weeks, but it may still need
one more week.
I am afraid it may have issues for dpdk 07 release, so send the v2 for
review first.
Thanks
> > >
> >
> > 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.
prev parent reply other threads:[~2025-06-16 2:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 7:41 Zhangfei Gao
2025-05-08 7:41 ` [PATCH 1/2] compress/uadk: use async mode to replace sync mode Zhangfei Gao
2025-05-08 7:41 ` [PATCH 2/2] crypto/uadk: " Zhangfei Gao
2025-05-21 12:39 ` [EXTERNAL] [PATCH 0/2] uadk: realize async mode Akhil Goyal
2025-05-22 10:02 ` Zhangfei Gao
2025-05-22 11:50 ` Akhil Goyal
2025-05-26 3:44 ` Zhangfei Gao
2025-05-26 6:15 ` Akhil Goyal
2025-06-04 12:04 ` Zhangfei Gao
2025-06-04 15:29 ` Akhil Goyal
2025-06-16 2:56 ` Zhangfei Gao [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABQgh9EXg94dopaqD-ReF51V699GZyiO7f3PzFbvK0AVsB3aQQ@mail.gmail.com \
--to=zhangfei.gao@linaro.org \
--cc=aconole@redhat.com \
--cc=ashishg@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
--cc=gakhil@marvell.com \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).