Hi all,
Currently DTS modifies some unit tests. We would like to drop these cases, only test the default instead.
I’ like to talk about it in the following meeting.
DTS unit suite which need modify dpdk code or add additional cmd to test.
|
DTS
suite |
Case |
Unit Test |
Comments |
Test Step |
|
unit_tests_loopback |
link_mode |
pmd_perf_autotest |
Need modify dpdk code to test
1, Disable loopback
2, Modify MAX_TRAFFIC_BURST from 2048 to 32
3, Add sleep for check link status |
sed -i -e 's/#define MAX_TRAFFIC_BURST 2048/#define MAX_TRAFFIC_BURST
32/' app/test/test_pmd_perf.c
sed -i -e 's/lpbk_mode = 1/lpbk_mode = 0/' app/test/test_pmd_perf.c
sed -i -e '/check_all_ports_link_status(nb_ports, RTE_PORT_ALL);/a\ sleep(6);' app/test/test_pmd_perf.c
rm -rf x86_64-native-linuxapp-gcc
CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=static x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:02:00.0 0000:02:00.1
x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 1-7 -n 4 -a 0000:02:00.0 -a 0000:02:00.1 --file-prefix=dpdk_18278_20220728104454
pmd_perf_autotest |
|
unit_tests_loopback |
loopback_mode |
pmd_perf_autotest |
Need modify dpdk code to test
1, Enable loopback by default.
2, Modify MAX_TRAFFIC_BURST from 2048 to 32
This case is same as “meson test with pmd_perf_autotest” + MAX_TRAFFIC_BURST=2048 by default |
sed -i -e 's/#define MAX_TRAFFIC_BURST 2048/#define
MAX_TRAFFIC_BURST 32/' app/test/test_pmd_perf.c
sed -i -e 's/lpbk_mode = 0/lpbk_mode = 1/' app/test/test_pmd_perf.c
----Default rm -rf x86_64-native-linuxapp-gcc CC=gcc meson -Denable_kmods=True -Dlibdir=lib --default-library=static x86_64-native-linuxapp-gcc ninja -C x86_64-native-linuxapp-gcc usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:02:00.0 0000:02:00.1 x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 1-7 -n 4 -a 0000:02:00.0 -a 0000:02:00.1 --file-prefix=dpdk_18278_20220728104454
pmd_perf_autotest |
|
unit_tests_pmd_perf |
pmd_burst |
pmd_perf_autotest |
Need add additional cmd to test |
x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 1-4 -n 4 -a 0000:02:00.0 -a 0000:02:00.1 --file-prefix=dpdk_28554_20220728123352
set_rxtx_sc poll_before_xmit
pmd_perf_autotest |
|
unit_tests_pmd_perf |
pmd_continues |
pmd_perf_autotest |
Need add additional cmd to test |
x86_64-native-linuxapp-gcc/app/test/dpdk-test -l 1-4 -n 4 -a 0000:02:00.0 -a 0000:02:00.1 --file-prefix=dpdk_28554_20220728123352
set_rxtx_sc continuous
set_rxtx_mode vector
set_rxtx_anchor rxtx
pmd_perf_autotest |
-----Original Appointment-----
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
Sent: Thursday, May 26, 2022 4:24 AM
To: Lincoln Lavoie; Owen Hilyard; Malla Malathi; David Marchand; Shepard Siegel; Jerin Jacob; scampbel@qti.qualcomm.com; Ali Alnubani; Tu, Lijuan; Zawadzki, Tomasz; Michael Santana; Honnappa Nagarahalli; erezsc@nvidia.com; bluca@debian.org; ktraynor@redhat.com;
Xu, Qian Q; Gal Cohen (Product); Maxime Coquelin; Ferruh Yigit; Richardson, Bruce; Ananyev Konstantin; Aaron Conole; Tkachuk, Georgii; Henry Nadeau; Hemant Agrawal; Wang, Liang-min; nishant.lodha@cavium.com; lixuming@huawei.com; Stokes, Ian; Mcnamara, John;
Liu, Yu Y; luca.boccassi@gmail.com; ci@dpdk.org; Zhang, Chun; juraj.linkes@pantheon.tech; Chen, Zhaoyan; Matz, Olivier; Stephen Hemminger; Thomas Monjalon; Ruifeng Wang (Arm Technology China); Erez Scop; O'Driscoll, Tim; Mike Leeson; Brandon Lo; Matt Spencer;
Zedlewski, Piotr; Kovacevic, Marko; Jerin Jacob Kollanukkaran; khemendra kumar; Nishant Lodha; nsouthern@linuxfoundation.org; mallam@gmail.com; ahassick@iol.unh.edu; jspewock@iol.unh.edu; Ashley Weltz; Trishan de Lanerolle
Subject: DPDK Community CI Testing Meeting
When: Occurs every 2 week(s) on Thursday effective 5/26/2022 until 12/31/2022 from 9:00 AM to 10:00 AM America/New_York.
Where: https://zoom.us/j/95952696590?pwd=b0JjVnJaWDZ3TW1XYjZKQkxmZUZuQT09
This event has been changed.
DPDK Community CI Testing Meeting
Topic: DPDK Testing & Community CI Labs Join Zoom Meeting Meeting ID: 959 5269 6590 Dial by your location Going (lijuan.tu@intel.com)? All
events in this series: Yes
- Maybe
- No more
options » |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Invitation from
Google Calendar You are receiving this courtesy email at the account
lijuan.tu@intel.com because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at
https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status,
or to modify your RSVP.
Learn More. |