- Acc - lists.linaro.org

by Zhangfei Gao

dpdk performance 12.1 https://docs.qq.com/doc/DRUNSWFlGeXRJSk1D 1. uadk  $ sudo dpdk-test-crypto-perf -l 1,2 --vdev crypto_uadk -- --devtype crypto_uadk --optype cipher-only --buffer-sz 64,128,256,512,1024,2048 --silent [sudo] password for linaro:  EAL: Detected CPU lcores: 128 EAL: Detected NUMA nodes: 4 EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: VFIO support initialized CRYPTODEV: Creating cryptodev crypto_uadk CRYPTODEV: Initialisation parameters - name: crypto_uadk,socket id: 0, max queue pairs: 8 TELEMETRY: No legacy callbacks, legacy socket not created Allocated pool "sess_mp_0" on socket 0     lcore id    Buf Size  Burst Size    Enqueued    Dequeued  Failed Enq  Failed Deq        MOps        Gbps  Cycles/Buf            2          64          32    10000000    10000000           0           0      0.8115      0.4155      123.23            2         128          32    10000000    10000000           0           0      0.7859      0.8048      127.24            2         256          32    10000000    10000000           0           0      0.7356      1.5066      135.93            2         512          32    10000000    10000000           0           0      0.6401      2.6219      156.23            2        1024          32    10000000    10000000           0           0      0.5186      4.2483      192.83            2        2048          32    10000000    10000000           0           0      0.3770      6.1774      265.22 $ sudo dpdk-test-crypto-perf -l 1,2 --vdev crypto_uadk -- --devtype crypto_uadk --buffer-sz 64,128,256,512,1024,2048 --optype cipher-then-auth --ptest throughput --auth-key-sz 64 --cipher-key-sz 16 --cipher-iv-sz 16 --auth-op generate --burst-sz 32 --total-ops 30000000 --silent --digest-sz 20 --auth-algo sha1-hmac --cipher-algo aes-cbc --cipher-op encrypt EAL: Detected CPU lcores: 128 EAL: Detected NUMA nodes: 4 EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: VFIO support initialized CRYPTODEV: Creating cryptodev crypto_uadk CRYPTODEV: Initialisation parameters - name: crypto_uadk,socket id: 0, max queue pairs: 8 TELEMETRY: No legacy callbacks, legacy socket not created Allocated pool "sess_mp_0" on socket 0     lcore id    Buf Size  Burst Size    Enqueued    Dequeued  Failed Enq  Failed Deq        MOps        Gbps  Cycles/Buf            2          64          32    30000000    30000000           0           0      0.3734      0.1912      267.80            2         128          32    30000000    30000000           0           0      0.3611      0.3698      276.90            2         256          32    30000000    30000000           0           0      0.3388      0.6939      295.16            2         512          32    30000000    30000000           0           0      0.2986      1.2230      334.92            2        1024          32    30000000    30000000           0           0      0.2419      1.9820      413.33            2        2048          32    30000000    30000000           0           0      0.1810      2.9661      552.37 2. openssl $ sudo dpdk-test-crypto-perf -l 1,2 --vdev crypto_openssl -- --devtype crypto_openssl --optype cipher-only --buffer-sz 64,128,256,512,1024,2048 --silent EAL: Detected CPU lcores: 128 EAL: Detected NUMA nodes: 4 EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: VFIO support initialized CRYPTODEV: Creating cryptodev crypto_openssl CRYPTODEV: Initialisation parameters - name: crypto_openssl,socket id: 0, max queue pairs: 8 TELEMETRY: No legacy callbacks, legacy socket not created Allocated pool "sess_mp_0" on socket 0     lcore id    Buf Size  Burst Size    Enqueued    Dequeued  Failed Enq  Failed Deq        MOps        Gbps  Cycles/Buf            2          64          32    10000000    10000000           0           0      3.5600      1.8227       28.09            2         128          32    10000000    10000000           0           0      2.9432      3.0138       33.98            2         256          32    10000000    10000000           0           0      2.2142      4.5347       45.16            2         512          32    10000000    10000000           0           0      1.4678      6.0122       68.13            2        1024          32    10000000    10000000           0           0      0.8805      7.2133      113.57            2        2048          32    10000000    10000000           0           0      0.4877      7.9898      205.06 $ sudo dpdk-test-crypto-perf -l 1,2 --vdev crypto_openssl -- --devtype crypto_openssl --buffer-sz 64,128,256,512,1024,2048 -- optype cipher-then-auth --ptest throughput --auth-key-sz 64 --cipher-key-sz 16 --cipher-iv-sz 16 --auth-op generate --burst-sz 32 --total-ops 30000 000 --silent --digest-sz 20 --auth-algo sha1-hmac --cipher-algo aes-cbc --cipher-op encrypt EAL: Detected CPU lcores: 128 EAL: Detected NUMA nodes: 4 EAL: Detected static linkage of DPDK EAL: Multi-process socket /var/run/dpdk/rte/mp_socket EAL: Selected IOVA mode 'VA' EAL: VFIO support initialized CRYPTODEV: Creating cryptodev crypto_openssl CRYPTODEV: Initialisation parameters - name: crypto_openssl,socket id: 0, max queue pairs: 8 TELEMETRY: No legacy callbacks, legacy socket not created Allocated pool "sess_mp_0" on socket 0     lcore id    Buf Size  Burst Size    Enqueued    Dequeued  Failed Enq  Failed Deq        MOps        Gbps  Cycles/Buf            2          64          32    30000000    30000000           0           0      0.9686      0.4959      103.24            2         128          32    30000000    30000000           0           0      0.8857      0.9069      112.91            2         256          32    30000000    30000000           0           0      0.7573      1.5510      132.05            2         512          32    30000000    30000000           0           0      0.5850      2.3964      170.93            2        1024          32    30000000    30000000           0           0      0.4017      3.2910      248.92            2        2048          32    30000000    30000000           0           0      0.2478      4.0601      403.54 3. Intel http://fast.dpdk.org/doc/perf/DPDK_22_07_Intel_crypto_performance_report.pdf

1 year, 5 months

1
0
0 0

Re: uadk branch & tag policy

by zhangfei.gao＠foxmail.com

On 2022/11/10 下午4:15, fanghao (A) wrote: > > > 在 2022/11/10 10:54, Zhangfei Gao 写道: >> Here is discussion about uadk branch & tag policy >> >> By now, I saw the best example >> https://github.com/intel/intel-ipsec-mb >> >> 1. no lts branch, only use tag + ReleaseNotes.txt >> >> Lts branch will cost too much resources, it is hard for a small team >> like us. >> For example it is difficult to git am current patch to any tag half >> year ago. >> >> Unlike OS, it is little meaning for UADK to keep a stable version. >> We can not attract customer only by maintaining a stable version, > mainly for LTS OS easy to catch the bugfix update for which version > that have been intergrated. Yes, but it maybe another story if we promise like two years' maintain. > >> but only the performance and new feautre, like support both >> accelerators and cpu instructions. >> >> >> 2. Tag policy >> >> Refer >> https://github.com/intel/intel-ipsec-mb/blob/main/ReleaseNotes.txt >> >> Basically two releases each year, > looks good to me. > >> >> v1.3 September 2022 >> v1.2 February 2022 >> v1.1 October 2021 >> v1.0 April 2021 >> > The time node is not fixed. Do we need fixed time? Sure, How about one month before Euler release? > >> No small tag, since uadk is stable enough. is it too simple, suitable? >> What's the minor tag used for? >> Other component (openssl-uadk) need refer these tag accordingly. >> >> We may consider minor tag for bug fix? like 1.3.1 for a big bug fix? > looks good to me. > >> intel-ipsec-mb$ >> $ git tag >> v1.0 >> v1.1 >> v1.2 >> v1.3 >> >> 3. ReleaseNotes Contents: >> >> General: >> Working combination, uadk xxx & openssl-uadk xxx & dpdk xxx >> >> Main change: >> Like support cpu instructions >> api change? >> >> Library >> New algoirthm: >> >> Test Applications: >> >> Fixes: >> > Can be simplified like this? > > Features： > ... > > Fixes: > ... We can use this for UADK. For openssl-uadk, the testing combination maybe required. I am not sure whether openssl-uadk can work with any version of UADK from now on. ie. the UADK interface keeps stable. We found openssl-uadk can not work with some old version UADK before. openssl-uadk depend on UADK, we can add testing combination in openssl-uadk ReleaseNotes. UADK releasenotes may have no such issue. > > > But how to kown the bugfix for which tag? > For example: new tag 2.3.1 for bugfix,how to kown this fix for which > version.maybe fix > for 2.1 just not for 2.3. Since no lts branch, only description in ReleaseNotes can be check. Since one release half year, suppose there is no such issue, like a bug fix happens half year later. Thanks > >> Release status: Unreleased & tag (like v1.3 September 2022) >> -Unreleased >> +v1.3 September 2022 >> >> _______________________________________________ >> Acc mailing list -- acc(a)openeuler.org >> To unsubscribe send an email to acc-leave(a)openeuler.org > _______________________________________________ > Acc mailing list -- acc(a)openeuler.org > To unsubscribe send an email to acc-leave(a)openeuler.org

1 year, 5 months

2
2
0 0

Fwd: DPDK 22.11 released

by Zhangfei Gao

-------- Forwarded Message -------- Subject: DPDK 22.11 released Date: Sun, 27 Nov 2022 23:22:17 +0100 From: Thomas Monjalon <thomas(a)monjalon.net> To: announce(a)dpdk.org A new major release is available: https://fast.dpdk.org/rel/dpdk-22.11.tar.xz It was a comfortable release cycle: 1387 commits from 193 authors 1902 files changed, 137224 insertions(+), 61256 deletions(-) The branch 22.11 should be supported for at least two years, maybe more, making it recommended for system integration and deployment. The new major ABI version is 23. The next releases 23.03 and 23.07 will be ABI-compatible with 22.11. Below are some new features: - LoongArch build - Intel uncore frequency control - mempool optimizations - new mbuf layout for IOVA-as-VA build - multiple mbuf pools per Rx queue - Rx buffer split based on protocol - hardware congestion management - hairpin memory configuration - proactive NIC error handling - Rx/Tx descriptor dump - flow API extensions - GVE (Google Virtual Ethernet) - IDPF (Intel Infrastructure DataPath Function) - UADK supporting HiSilicon crypto - MACsec processing offload - ShangMi crypto algorithms - baseband FFT operations - eventdev Tx queue start/stop - eventdev crypto vectorization - NitroSketch membership - DTS introduction in DPDK repository More details in the release notes: https://doc.dpdk.org/guides/rel_notes/release_22_11.html There are 74 new contributors (including authors, reviewers and testers). Welcome to Abdullah Sevincer, Abhishek Maheshwari, Alan Liu, Aleksandr Miloshenko, Alex Vesker, Alexander Chernavin, Allen Hubbe, Amit Prakash Shukla, Anatolii Gerasymenko, Arkadiusz Kubalewski, Arshdeep Kaur, Benjamin Le Berre, Bhagyada Modali, David MacDougal, Dawid Zielinski, Dexia Li, Dukai Yuan, Erez Shitrit, Fei Qin, Frank Du, Gal Shalom, Grzegorz Siwik, Hamdan Igbaria, Hamza Khan, Henning Schild, Huang Wei, Huzaifa Rahman, James Hershaw, Jeremy Spewock, Jin Ling, Joey Xing, Jun Qiu, Kaiwen Deng, Karen Sornek, Ke Xu, Kevin O'Sullivan, Lei Cai, Lei Ji, Leszek Zygo, Long Wu, Lukasz Czapnik, Lukasz Kupczak, Mah Yock Gen, Mandal Purna Chandra, Mao YingMing, Marcin Szycik, Michael Savisko, Min Zhou, Mingjin Ye, Mingshan Zhang, Mário Kuka, Piotr Gardocki, Qingmin Liu, R Mohamed Shah, Roman Storozhenko, Sathesh Edara, Sergey Temerkhanov, Shiqi Liu, Stephen Coleman, Steven Zou, Sunil Uttarwar, Sunyang Wu, Sylvia Grundwürmer, Tadhg Kearney, Taekyung Kim, Taripin Samuel, Tomasz Jonak, Tomasz Zawadzki, Tsotne Chakhvadze, Usman Tanveer, Wiktor Pilarczyk, Yaqi Tang, Yi Li and Zhangfei Gao. Below is the number of commits per employer (with authors count): 456 Intel (65) 227 Marvell (29) 179 NVIDIA (28) 83 Corigine (6) 81 Red Hat (5) 60 Huawei (6) 58 AMD (5) 55 Microsoft (4) 53 OKTET Labs (2) 19 NXP (5) 14 Ericsson (1) 13 6WIND (2) ... A big thank to all courageous people who took on the non rewarding task of reviewing other's job. Based on Reviewed-by and Acked-by tags, the top non-PMD reviewers are: 53 Akhil Goyal <gakhil(a)marvell.com> 45 Andrew Rybchenko <andrew.rybchenko(a)oktetlabs.ru> 36 Morten Brørup <mb(a)smartsharesystems.com> 34 Niklas Söderlund <niklas.soderlund(a)corigine.com> 34 Bruce Richardson <bruce.richardson(a)intel.com> 33 David Marchand <david.marchand(a)redhat.com> 31 Ori Kam <orika(a)nvidia.com> 25 Maxime Coquelin <maxime.coquelin(a)redhat.com> 21 Jerin Jacob <jerinj(a)marvell.com> 20 Chengwen Feng <fengchengwen(a)huawei.com> The next version will be 23.03 in March. The new features for 23.03 can be submitted during the next 4 weeks: http://core.dpdk.org/roadmap#dates Please share your roadmap. Thanks everyone

1 year, 5 months

1
0
0 0

Urgent Asap!!!!.....

by John Bill

Good day, Did you get my last email? I have sent email 3 times and no reply from you. Hope this email acc(a)lists.linaro.org is correct I await your prompt response. Yours sincerely, Best regards,

1 year, 5 months

1
0
0 0

[PATCH v6 0/3] uadk: adjust header file

by liulongfang

Sort out the current file inclusion relationship of uadk, and adjust the inclusion order of some header files. Changes v5 -> v6: Remove the modification in wd_alg_common.h Changes v4 -> v5: Remove the interface and move to wd_util.h. Changes v3 -> v4: Rebase on wd_comp_init2 patches. Changes v2 -> v3: Update file relationship diagram Changes v1 -> v2: adjust the content of wd_alg_common.h liulongfang (3): uadk: Remove duplicate header files uadk: adjust header file include logic uadk: add a file structure diagram Makefile.am | 2 +- docs/uadk_file_relationship.svg | 40 +++++++++++++++++++++++++++++++++ drv/hisi_comp.c | 1 - drv/hisi_qm_udrv.c | 1 + drv/hisi_sec.c | 4 ---- include/drv/wd_aead_drv.h | 3 +-- include/drv/wd_cipher_drv.h | 4 ++-- include/drv/wd_comp_drv.h | 4 ++-- include/drv/wd_dh_drv.h | 3 ++- include/drv/wd_digest_drv.h | 3 +-- include/drv/wd_ecc_drv.h | 2 +- include/drv/wd_rsa_drv.h | 1 + include/hisi_qm_udrv.h | 3 +-- include/wd.h | 17 ++++++++++---- include/wd_aead.h | 2 -- include/wd_alg_common.h | 10 ++++----- include/wd_cipher.h | 1 - include/wd_common.h | 23 ------------------- include/wd_comp.h | 2 +- include/wd_dh.h | 5 ----- include/wd_digest.h | 1 - include/wd_ecc.h | 1 - include/wd_rsa.h | 4 ---- include/wd_util.h | 3 ++- wd.c | 1 - wd_aead.c | 1 - wd_cipher.c | 1 - wd_comp.c | 3 --- wd_dh.c | 2 -- wd_digest.c | 1 - wd_ecc.c | 1 - wd_rsa.c | 3 +-- wd_util.c | 1 - 33 files changed, 74 insertions(+), 80 deletions(-) create mode 100644 docs/uadk_file_relationship.svg delete mode 100644 include/wd_common.h -- 2.33.0

1 year, 5 months

1
3
0 0

[PATCH v5 0/2] uadk: adjust header file

by liulongfang

1 year, 5 months

3
4
0 0

dpdk compress code

by Zhangfei Gao

dpdk compress code is almost ready. https://github.com/Linaro/dpdk/tree/next-11.24-compress. The dpdk only support deflate,  We added some hack to use zlib, which will be removed when testing deflate -                       setup.alg_type = WD_ZLIB; +                       setup.alg_type = WD_DEFLATE; -       udev = wd_get_accel_dev("zlib"); +       udev = wd_get_accel_dev("deflate"); Test: https://github.com/Linaro/dpdk/blob/next-11.24-compress/doc/guides/compress… Prepare hugepage, only one time echo 1024 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages echo 1024 > /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages echo 1024 > /sys/devices/system/node/node2/hugepages/hugepages-2048kB/nr_hugepages echo 1024 > /sys/devices/system/node/node3/hugepages/hugepages-2048kB/nr_hugepages mkdir -p /mnt/huge_2mb mount -t hugetlbfs none /mnt/huge_2mb -o pagesize=2MB Test app     sudo dpdk-test --vdev=compress_uadk     RTE>>compressdev_autotest     RTE>>quit  

1 year, 5 months

1
0
0 0

ci builder.sh can be used on both ARM and X86

by Zhangfei Gao

ci builder.sh can be used on both ARM and X86 ARM: build and sanity_test  X86: only build $ git clone https://git.linaro.org/ci/job/configs $ cd configs/uadk Fetch pull request accordingly, for example, testing https://github.com/Linaro/uadk/pull/529 Need manually change uadk/builders.sh. diff --git a/uadk/builders.sh b/uadk/builders.sh index 28f55178b..2ca49cfd8 100755 --- a/uadk/builders.sh +++ b/uadk/builders.sh @@ -105,6 +105,7 @@ check_existed_repo() {                         git clone --depth 1 https://github.com/Linaro/uadk.git                 fi                 cd ${WORKSPACE}/uadk +               git pull origin pull/529/head                 ;;         "ssluadk")                 if [ ! -d ${WORKSPACE}/uadk_engine ]; then $ ./builder.sh  

1 year, 5 months

1
0
0 0

subscribe

by Yang Shen

subscribe  subscribe

1 year, 6 months

1
0
0 0

uadk branch & tag policy

by Zhangfei Gao

Here is discussion about uadk branch & tag policy By now, I saw the best example https://github.com/intel/intel-ipsec-mb 1. no lts branch, only use tag + ReleaseNotes.txt Lts branch will cost too much resources, it is hard for a small team like us. For example it is difficult to git am current patch to any tag half year ago. Unlike OS, it is little meaning for UADK to keep a stable version. We can not attract customer only by maintaining a stable version,  but only the performance and new feautre, like support both accelerators and cpu instructions. 2. Tag policy Refer https://github.com/intel/intel-ipsec-mb/blob/main/ReleaseNotes.txt Basically two releases each year,  v1.3 September 2022 v1.2 February 2022 v1.1 October 2021 v1.0 April 2021 No small tag, since uadk is stable enough. is it too simple, suitable? What's the minor tag used for?  Other component (openssl-uadk) need refer these tag accordingly. We may consider minor tag for bug fix? like 1.3.1 for a big bug fix?   intel-ipsec-mb$ $ git tag v1.0 v1.1 v1.2 v1.3 3. ReleaseNotes Contents: General: Working combination, uadk xxx & openssl-uadk xxx & dpdk xxx Main change: Like support cpu instructions api change? Library New algoirthm: Test Applications: Fixes: Release status: Unreleased & tag (like v1.3 September 2022) -Unreleased +v1.3 September 2022  

1 year, 6 months

1
0
0 0

2024

2023

2022

Acc

2024

2023

2022

Acc ----- 2024 ----- May 2024 April 2024 March 2024 February 2024 January 2024 ----- 2023 ----- December 2023 November 2023 October 2023 September 2023 August 2023 July 2023 June 2023 May 2023 April 2023 March 2023 February 2023 January 2023 ----- 2022 ----- December 2022 November 2022

Acc