From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 8887FA0509; Wed, 6 Apr 2022 10:41:07 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6CB7E40E2D; Wed, 6 Apr 2022 10:41:07 +0200 (CEST) Received: from smtp-relay-internal-0.canonical.com (smtp-relay-internal-0.canonical.com [185.125.188.122]) by mails.dpdk.org (Postfix) with ESMTP id F168840689 for ; Wed, 6 Apr 2022 10:41:05 +0200 (CEST) Received: from mail-qv1-f69.google.com (mail-qv1-f69.google.com [209.85.219.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-0.canonical.com (Postfix) with ESMTPS id B04173F20F for ; Wed, 6 Apr 2022 08:41:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1649234464; bh=sfRYMk6VF+xpRUXNYJ6fuL0h92axEWENpujvldpjEXY=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=WT9IUZ2Za7vZUPDYlR29l0fRaQXo05KlOhFhQQ0zotVprzg5Dt3opOw0zBNbJG+WH 3auRz7NUVkCX+ALcEorKWeySM4JHQBuQ7RehKThhT0alJ+HOhe5DB/KkqpEKJ6kjIl DrubUq8JoNkEjXjMXumiXh3+oq+CSVfzMn0isiF27gj35qpiXimaaBREl9hW+I5K6+ ThT2rrPhZ6y1rFTkv6z/82DnCKQ6t6gClTqjwzXy2wq/3ywwmVkpYIB1EY3+rdlld3 enHkLwrfpE8uId9LI8/E+Xob1H44T+OpayF1NiY0ymu/IPOuH3F2RRaSM08K/f+B3G C5uvsT9B39cqw== Received: by mail-qv1-f69.google.com with SMTP id 33-20020a0c8024000000b0043d17ffb0bdso2614158qva.18 for ; Wed, 06 Apr 2022 01:41:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sfRYMk6VF+xpRUXNYJ6fuL0h92axEWENpujvldpjEXY=; b=F4HE9r5PPL/7Q8EDgxD8nj9Kiw0MaQBB7HBKdgnxJgp5NtkXR7iaj+kn0mbQJXpich /q+aNiSofoMOR05SNxkdcHchB01LOZY8XC/4wSIQ9wUxorS3zvXV/C3Eq+BevX8bl+ZO h7I1bT5nt6A1HOW/m4mOGeEsWPF3il1T0Rotkn7YTeK/BJcbs4Khple5lrrtbs+AOXMs qGqGTa9zHBBo/AU77+aMzRuwlvKoYeSwtzBgYgADg65yQxrLdmIsm/aC1fP3IdU1DFsY y53oe1nx7BbOr51M79dHYUNlg6hGloxf1X8HtoN4acko6e1vIlkERNQ7+1cigPRExq28 VjZA== X-Gm-Message-State: AOAM531VQfbELxWizBOoeNqF+1KLSp/sCysGW1TbvF6bdBp+qNkEjEzg cFIzw3CfQ0l8/PeWnEAi7aHT3dhaE0EU8q7aVyX9rApoItmc/25Dm3L4BZt8/gmV/RyhSReP8WV hRW1TZacSwuOpwZBwNW0tlE6mXgRcJckLUg1e X-Received: by 2002:a05:620a:f03:b0:67e:1e38:4a0 with SMTP id v3-20020a05620a0f0300b0067e1e3804a0mr4911882qkl.86.1649234450400; Wed, 06 Apr 2022 01:40:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzkQIT/dqxLKnrimMbN7KlwsAAt7uCHzFWdyQSptncztwzbwDB6C3z7cgohKOM8n2FRCSM0DjmllklcZmp0Tks= X-Received: by 2002:a05:620a:f03:b0:67e:1e38:4a0 with SMTP id v3-20020a05620a0f0300b0067e1e3804a0mr4911862qkl.86.1649234450141; Wed, 06 Apr 2022 01:40:50 -0700 (PDT) MIME-Version: 1.0 References: <20220321115516.3986382-1-christian.ehrhardt@canonical.com> In-Reply-To: From: Christian Ehrhardt Date: Wed, 6 Apr 2022 10:40:24 +0200 Message-ID: Subject: Re: 19.11.12 patches review and test To: "Jiang, YuX" Cc: "Yang, SteveX" , "Zhang, Roy Fan" , "stable@dpdk.org" , "dev@dpdk.org" , Abhishek Marathe , Ali Alnubani , "Walker, Benjamin" , David Christensen , "hariprasad.govindharajan@intel.com" , Hemant Agrawal , "Stokes, Ian" , Jerin Jacob , "Mcnamara, John" , Ju-Hyoung Lee , Kevin Traynor , Luca Boccassi , Pei Zhang , "Xu, Qian Q" , Raslan Darawsheh , Thomas Monjalon , "Peng, Yuan" , "Chen, Zhaoyan" Content-Type: multipart/alternative; boundary="0000000000008d676405dbf851ce" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --0000000000008d676405dbf851ce Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Apr 6, 2022 at 9:05 AM Jiang, YuX wrote: > *From:* Christian Ehrhardt > *Sent:* Wednesday, April 6, 2022 2:49 PM > *To:* Jiang, YuX > *Cc:* stable@dpdk.org; dev@dpdk.org; Abhishek Marathe < > Abhishek.Marathe@microsoft.com>; Ali Alnubani ; > Walker, Benjamin ; David Christensen < > drc@linux.vnet.ibm.com>; hariprasad.govindharajan@intel.com; Hemant > Agrawal ; Stokes, Ian ; > Jerin Jacob ; Mcnamara, John ; > Ju-Hyoung Lee ; Kevin Traynor = ; > Luca Boccassi ; Pei Zhang ; Xu, > Qian Q ; Raslan Darawsheh ; > Thomas Monjalon ; Peng, Yuan ; > Chen, Zhaoyan > *Subject:* Re: 19.11.12 patches review and test > > > > > > > > On Thu, Mar 31, 2022 at 12:00 PM Christian Ehrhardt < > christian.ehrhardt@canonical.com> wrote: > > > > > > On Wed, Mar 30, 2022 at 1:04 PM Jiang, YuX wrote: > > > -----Original Message----- > > From: christian.ehrhardt@canonical.com > > > Sent: Monday, March 21, 2022 7:55 PM > > To: stable@dpdk.org > > Cc: dev@dpdk.org; Abhishek Marathe ; > > Ali Alnubani ; Walker, Benjamin > > ; David Christensen > > ; hariprasad.govindharajan@intel.com; Hemant > > Agrawal ; Stokes, Ian ; > > Jerin Jacob ; Mcnamara, John > > ; Ju-Hyoung Lee ; > > Kevin Traynor ; Luca Boccassi ; > > Pei Zhang ; Xu, Qian Q ; > > Raslan Darawsheh ; Thomas Monjalon > > ; Peng, Yuan ; Chen, > > Zhaoyan > > Subject: 19.11.12 patches review and test > > > > Hi all, > > > > Here is a list of patches targeted for stable release 19.11.12. > > > > The planned date for the final release is 7th of April. > > > > Please help with testing and validation of your use cases and report an= y > > issues/results with reply-all to this mail. For the final release the > fixes and > > reported validations will be added to the release notes. > > > > A release candidate tarball can be found at: > > > > https://dpdk.org/browse/dpdk-stable/tag/?id=3Dv19.11.12-rc1 > > > > These patches are located at branch 19.11 of dpdk-stable repo: > > https://dpdk.org/browse/dpdk-stable/ > > > > Thanks. > > > > Christian Ehrhardt > > > Update the test status for Intel part. DPDK19.11.12-rc1 test rate is 60%, > totally find four defects as below: > > > > Hi Christian, > > > > Bug1: [dpdk-19.11.12] metering_and_policing/ipv4_HASH_table_RFC2698: > unable to forward packets normally. Intel Dev is investigating. > > First test with 4ports, also can reproduce with 19.11, confirmed > with Dev -- not fixed yet, but also not too bad (or not a regression to t= he > former state) and thereby does not block 19.11.12 > > Thanks, if down the road there is a fix feel free to send it to stable@ as usual. Bug2: [LTS DPDK-19.11.12-rc1] cryptodev_qat_asym_autotest is failing. Intel > Dev is investigating. Bad commit: commit > d2b406a1da4f4cbc1f6a1b1940659819e2ae2d34 > > Confirmed with Dev, need revert the commit which is sent for > 21.xx fix but not for 19.11 LTS, and validation team test passed after > revert the commit. > > Thanks for the reply! This was added in 19.11.11 and not found back then, glad you got it now. Since this is Intel Test (you) + Intel Dev (You and the Devs you confirmed it with) and an Intel Device I'll take your word and will revert this in 19.11.12. There is no need to tag an -rc2 for it since you already tested the most relevant devices/tests with that revert (and no one else saw it before or after the change in 19.11.11). > Bug3: https://bugs.dpdk.org/show_bug.cgi?id=3D978 [dpdk-19.11.12-rc1] > drivers/net/qede make build failed on Fedora35 with Clang13.0.0.( may dup= : > https://bugs.dpdk.org/show_bug.cgi?id=3D912) > > Bad commit from Vanshika Shukla , no fix > yet. > > Bug4: https://bugs.dpdk.org/show_bug.cgi?id=3D977 [dpdk-19.11.12-rc1] > bnxt_stats meson&&make build Error on Fedora35-64 and Ubuntu2110-64 with > gcc11.2.1&&gcc11.2.0. =C3=A0Fixed by latest LTS19.11 > > > > Thank you for all your work! > > > > Bug1:[dpdk-19.11.12] metering_and_policing/ipv4_HASH_table_RFC2698: unabl= e > to forward packets normally. Intel Dev is investigating. > Bug2:[LTS DPDK-19.11.12-rc1] cryptodev_qat_asym_autotest is failing. Inte= l > Dev is investigating. > > > > Both are very interesting, could you make sure that by next Wednesday (6t= h > of April) there is feedback on this thread if this is either: > > > > Hi Jiang YuX, > > by now everything else is in place to tag the 19.11.12 release tomorrow, > > therefore I wanted to ping for these updates so that we can make the righ= t > decision to release or delay. > > > > 1. fixable, with a pointer to a fix > > 2. not fixed yet, but also not too bad (or not a regression to the former > state) and thereby does not block 19.11.12 > > 3. not fixed yet, but being very severe blocking 19.11.12, but identified > the offending commit that shall be reverted > > 4. not fixed yet, but being very severe blocking 19.11.12, and an ETA of = a > fix/mitigation > > > > Based on that outcome we then need to decide if we need to tag -rc2 and > another round of verifications. > > > > Bug3:https://bugs.dpdk.org/show_bug.cgi?id=3D978 [dpdk-19.11.12-rc1] > drivers/net/qede make build failed on Fedora35 with Clang13.0.0. > > Bad commit from Vanshika Shukla , no fix yet. > > > > Thanks for identifying this one. > > As in the past, we are willing to take build time fixes for newer compile= r > stacks, but we are not blocked on releasing 19.11.12 unless platforms > formerly building and using it are affected. > > > > Bug4:https://bugs.dpdk.org/show_bug.cgi?id=3D977 [dpdk-19.11.12-rc1] > bnxt_stats meson&&make build Error on Fedora35-64 and Ubuntu2110-64 with > gcc11.2.1&&gcc11.2.0. > > Has fix ( > https://github.com/cpaelzer/dpdk-stable-queue/commit/f17a5eb33a2fec2f3347= 6743f56d1fb2d37ca3b7.patch) > and verify passed. > > > > Yes thanks, this one is indeed already applied > > > > > # Basic Intel(R) NIC testing > * Build: cover the build test combination with latest GCC/Clang/ICC > version and the popular OS revision such as Ubuntu20.04, Fedora35, RHEL8.= 4, > etc. > - All test done. Two new bugs are found, and one known bug( > https://bugs.dpdk.org/show_bug.cgi?id=3D747) > * PF(i40e, ixgbe): test scenarios including > RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. > - Execution rate is 30%, no new issue is found. > * VF(i40e, ixgbe): test scenarios including > VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. > - Execution rate is 30%, no new issue is found. > * PF/VF(ice): test scenarios including Switch features/Package > Management/Flow Director/Advanced Tx, etc. > - All test done. No new issue is found. > * Intel NIC single core/NIC performance: test scenarios including PF/VF > single core performance test etc. > - All test done. No big performance drop. > * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test > - QAT&SW/FIB library, etc. > - On going. > # Basic cryptodev and virtio testing > * Virtio: both function and performance test are covered. Such as > PVP/Virtio_loopback/virtio-user loopback/virtio-net VM2VM perf testing, e= tc. > - All test done. No new issue is found. > * Cryptodev: > * Function test: test scenarios including Cryptodev API > testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/ etc. > - On going. > * Performance test: test scenarios including Thoughput Performance > /Cryptodev Latency, etc. > - On going. > > BRs > Yu Jiang > > > > > -- > > Christian Ehrhardt > Staff Engineer, Ubuntu Server > Canonical Ltd > > > > > -- > > Christian Ehrhardt > Staff Engineer, Ubuntu Server > Canonical Ltd > --=20 Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd --0000000000008d676405dbf851ce Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Apr 6, 2022 at 9:05 AM Jiang,= YuX <yux.jiang@intel.com>= wrote:

From: Christian Ehrhardt <christian.ehrhardt@ca= nonical.com>
Sent: Wednesday, April 6, 2022 2:49 PM
To: Jiang, YuX <yux.jiang@intel.com>
Cc: stable@dpdk= .org; dev@dpdk.org; Abhishek Marathe <Abhishek.Marathe@microsoft.com>; Ali Alnubani <<= a href=3D"mailto:alialnu@nvidia.com" target=3D"_blank">alialnu@nvidia.com>; Walker, Benjamin <benjamin.walker@intel.com>; David Christensen <<= a href=3D"mailto:drc@linux.vnet.ibm.com" target=3D"_blank">drc@linux.vnet.i= bm.com>; hariprasad.govindharajan@intel.com; Hemant Agrawal <he= mant.agrawal@nxp.com>; Stokes, Ian <ian.stokes@intel.com>; Jerin Jacob <= jerinj@marvell.com<= /a>>; Mcnamara, John <john.mcnamara@intel.com>; Ju-Hyoung Lee <juhlee@microsoft.com>= ;; Kevin Traynor <ktraynor@redhat.com>; Luca Boccassi <bluca@debian.org>; Pei Zhang <pezhang@= redhat.com>; Xu, Qian Q <qian.q.xu@intel.com>; Raslan Darawsheh <rasland@nvidia.com>= ; Thomas Monjalon <thomas@monjalon.net>; Peng, Yuan <yuan.peng@intel.com>; Chen, Zhaoyan &l= t;zhaoyan.chen@= intel.com>
Subject: Re: 19.11.12 patches review and test

=C2=A0

=C2=A0

=C2=A0

On Thu, Mar 31, 2022 at 12:00 PM Christian Ehrhardt = <c= hristian.ehrhardt@canonical.com> wrote:

=C2=A0

=C2=A0

On Wed, Mar 30, 2022 at 1:04 PM Jiang, YuX <yux.jiang@intel.com= > wrote:

> -----Original Message-----
> From: christian.ehrhardt@canonical.com <christian.ehrhardt@canonical.com<= /a>>
> Sent: Monday, March 21, 2022 7:55 PM
> To: stable@dpdk.o= rg
> Cc: dev@dpdk.org= ; Abhishek Marathe <Abhishek.Marathe@microsoft.com>;
> Ali Alnubani <alialnu@nvidia.com>; Walker, Benjamin
> <ben= jamin.walker@intel.com>; David Christensen
> <drc@li= nux.vnet.ibm.com>; har= iprasad.govindharajan@intel.com; Hemant
> Agrawal <hemant.agrawal@nxp.com>; Stokes, Ian <ian.stokes@intel.com>;
> Jerin Jacob <jerinj@marvell.com>; Mcnamara, John
> <john.= mcnamara@intel.com>; Ju-Hyoung Lee <juhlee@microsoft.com>;
> Kevin Traynor <ktraynor@redhat.com>; Luca Boccassi <bluca@debian.org>;
> Pei Zhang <= pezhang@redhat.com>; Xu, Qian Q <qian.q.xu@intel.com>;
> Raslan Darawsheh <rasland@nvidia.com>; Thomas Monjalon
> <thomas@mo= njalon.net>; Peng, Yuan <yuan.peng@intel.com>; Chen,
> Zhaoyan <zhaoyan.chen@intel.com>
> Subject: 19.11.12 patches review and test
>
> Hi all,
>
> Here is a list of patches targeted for stable release 19.11.12.
>
> The planned date for the final release is 7th of April.
>
> Please help with testing and validation of your use cases and report a= ny
> issues/results with reply-all to this mail. For the final release the = fixes and
> reported validations will be added to the release notes.
>
> A release candidate tarball can be found at:
>
>=C2=A0 =C2=A0 =C2=A0https://dpdk.org/browse/dpdk-stable/= tag/?id=3Dv19.11.12-rc1
>
> These patches are located at branch 19.11 of dpdk-stable repo:
>=C2=A0 =C2=A0 =C2=A0https://dpdk.org/browse/dpdk-stable/
>
> Thanks.
>
> Christian Ehrhardt <christian.ehrhardt@canonical.com>
>
Update the test status for Intel part. DPDK19.11.12-rc1 test rate is 60%, t= otally find four defects as below:

=C2=A0

Hi Christian,

=C2=A0

Bug1: [dpdk-19.11.12] = metering_and_policing/ipv4_HASH_table_RFC2698: unable to forward packets no= rmally. Intel Dev is investigating.

=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 First test with 4ports, also can reproduce with= 19.11, confirmed with Dev -- not fixed yet, but also not too bad (or not a= regression to the former state) and thereby does not block 19.11.12=C2=A0<= /p>


Thanks, if down the road there is a fix feel free to = send it to stable@ as usual.

=

Bug2: [LTS DPDK-19.11.= 12-rc1] cryptodev_qat_asym_autotest is failing. Intel Dev is investigating.= Bad commit: commit d2b406a1da4f4cbc1f6a1b1940659819e2ae2d34<= /p>

=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0 Confirmed with Dev, need revert the commit which is sent for 21.xx fix but not for 19.11 LTS, and va= lidation team test passed after revert the commit.


=

Thanks for the repl= y!
This was added in 19.11.11 and not found back then, glad you g= ot it now.

Since this is Intel Test (you)=C2= =A0+ Intel Dev (You and the Devs you confirmed it with) and an Intel Device= I'll take your word and will revert this in 19.11.12.
There = is no need to tag an -rc2 for it since you already tested the most relevant= devices/tests with that revert (and no one else saw it before or after the= change in 19.11.11).
=C2=A0
=

Bug3: https://bugs.dpdk= .org/show_bug.cgi?id=3D978 [dpdk-19.11.12-rc1] drivers/net/qede make bu= ild failed on Fedora35 with Clang13.0.0.( may dup: https://bugs.dpdk.org/sho= w_bug.cgi?id=3D912)

=C2=A0=C2=A0=C2=A0 =C2= =A0=C2=A0=C2=A0Bad commit from Vanshika Shukla <vanshika.shukla@nxp.com>, no fi= x yet.

Bug4: https://bugs.dpdk= .org/show_bug.cgi?id=3D977 [dpdk-19.11.12-rc1] bnxt_stats meson&&am= p;make build Error on Fedora35-64 and Ubuntu2110-64 with gcc11.2.1&&= ;gcc11.2.0.=C2=A0 =C3=A0Fixed by latest LTS19.11=

=C2=A0

Thank you for all your work!

=C2=A0

Bug1:[dpdk-19.11.12] metering_and_policing/ipv4_HASH= _table_RFC2698: unable to forward packets normally. Intel Dev is investigat= ing.
Bug2:[LTS DPDK-19.11.12-rc1] cryptodev_qat_asym_autotest is failing. Intel = Dev is investigating.

=C2=A0

Both are very interesting, could you make sure that = by next Wednesday (6th of April) there is feedback on this thread if this i= s either:

=C2=A0

Hi=C2=A0Jiang YuX,

by now everything else is in place to tag the 19.11.= 12 release tomorrow,

therefore I wanted to ping for these updates so that= we can make the right decision to release or delay.

=C2=A0

1. fixable, with a pointer to a fix

2. not fixed yet, but also not too bad (or not a reg= ression to the former state) and thereby does not block 19.11.12<= /u>

3. not fixed yet, but being very severe blocking 19.= 11.12, but identified the offending=C2=A0commit that shall be reverted

4. not fixed yet, but being very severe blocking 19.= 11.12, and an ETA of a fix/mitigation

=C2=A0

Based on that outcome we then need to decide if we n= eed to tag -rc2 and another round of verifications.

=C2=A0

Bug3:https://bugs.dpdk.org/show_bug.cgi?id=3D978 = [dpdk-19.11.12-rc1] drivers/net/qede make build failed on Fedora35 with Cla= ng13.0.0.
> Bad commit from Vanshika Shukla <vanshika.shukla@nxp.com>, no fix yet.<= /u>

=C2=A0

Thanks for identifying this one.

As in the past, we are willing to take build time fi= xes for newer compiler stacks, but we are not blocked on releasing 19.11.12= unless platforms formerly building and using it are affected.

=C2=A0

Bug4:https://bugs.dpdk.org/show_bug.cgi?id=3D977 = [dpdk-19.11.12-rc1] bnxt_stats meson&&make build Error on Fedora35-= 64 and Ubuntu2110-64 with gcc11.2.1&&gcc11.2.0.
> Has fix (https:= //github.com/cpaelzer/dpdk-stable-queue/commit/f17a5eb33a2fec2f33476743f56d= 1fb2d37ca3b7.patch) and verify passed.

=C2=A0

Yes thanks, this one is indeed already applied

=C2=A0


# Basic Intel(R) NIC testing
* Build: cover the build test combination with latest GCC/Clang/ICC version= and the popular OS revision such as Ubuntu20.04, Fedora35, RHEL8.4, etc. - All test done. Two new bugs are found, and one known bug(https://bugs.dpdk= .org/show_bug.cgi?id=3D747)
* PF(i40e, ixgbe): test scenarios including RTE_FLOW/TSO/Jumboframe/checksu= m offload/VLAN/VXLAN, etc.
- Execution rate is 30%, no new issue is found.
* VF(i40e, ixgbe): test scenarios including VF-RTE_FLOW/TSO/Jumboframe/chec= ksum offload/VLAN/VXLAN, etc.=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0
- Execution rate is 30%, no new issue is found.
* PF/VF(ice): test scenarios including Switch features/Package Management/F= low Director/Advanced Tx, etc.
- All test done. No new issue is found.
* Intel NIC single core/NIC performance: test scenarios including PF/VF sin= gle core performance test etc.
- All test done. No big performance drop.
* IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test -= QAT&SW/FIB library, etc.
- On going.=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0
# Basic cryptodev and virtio testing
* Virtio: both function and performance test are covered. Such as PVP/Virti= o_loopback/virtio-user loopback/virtio-net VM2VM perf testing, etc.
- All test done. No new issue is found.
* Cryptodev:
* Function test: test scenarios including Cryptodev API testing/CompressDev= ISA-L/QAT/ZLIB PMD Testing/ etc.
- On going.
* Performance test: test scenarios including Thoughput Performance /Cryptod= ev Latency, etc.
- On going.

BRs
Yu Jiang


=C2=A0

--

Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd


=C2=A0

--

Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd



--
Christian Ehrhardt
Staff Engineer, Ubuntu Ser= ver
Canonical Ltd
--0000000000008d676405dbf851ce--