From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: dts@dpdk.org, ci@dpdk.org,
Paul Szczepanek <Paul.Szczepanek@arm.com>,
Luca Vizzarro <Luca.Vizzarro@arm.com>,
Nicholas Pratte <npratte@iol.unh.edu>,
Dean Marx <dmarx@iol.unh.edu>,
Thomas Wilks <thomas.wilks@arm.com>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>
Subject: DPDK 25.03 DPDK Test Suite Roadmap
Date: Thu, 12 Dec 2024 17:24:06 -0500 [thread overview]
Message-ID: <CAJvnSUA1gtvVyzSEqBdErYXSwRAeijj5MCOvcxPr5GF3O0ANrA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3061 bytes --]
25.03 DTS Roadmap
Below is the 25.03 DTS Roadmap. There are both some carry over series from
the previous (24.11) development cycle which are ongoing, as well as new
items.
1.
Add virtual function configuration support
1.
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1500
2.
Patchwork: https://patchwork.dpdk.org/project/dpdk/list/?series=33109
2.
Support flow rules via a DPDK flow rule dataclass, and port over legacy
rte_flow testsuite:
1.
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1486
2.
Patchwork: https://patches.dpdk.org/project/dpdk/list/?series=34104
3.
Support per-testsuite config values in conf.yaml
1.
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1375
4.
Update conf.yaml such that each port’s bus info has to be defined only
once, instead of twice under two different nodes (local node and peer node)
1.
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1478
2.
Patchwork: https://patches.dpdk.org/project/dpdk/list/?series=32804
5.
Remove excess attributes from conf.yaml DTS configuration
1.
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1360
6.
Split test_run and node configuration into separate files
1.
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1344
2.
Patchwork: https://patches.dpdk.org/project/dpdk/list/?series=32384
7.
Replace current linters with Ruff:
1.
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1358
2.
Patchwork: https://patches.dpdk.org/project/dpdk/list/?series=34141
8.
Copy dpdk-devbind to both hosts (currently only available on SUT) and
bind according to TG and DPDK requirements
1.
https://bugs.dpdk.org/show_bug.cgi?id=1420
9.
Write traffic generator subclass for TREX and one other performance TG
1.
https://bugs.dpdk.org/show_bug.cgi?id=1601
10.
Port over single core forwarding performance test
11.
Clean up DPDK source artifacts at the conclusion of a test run (delete
DPDK tarballs, devbind script, etc.)
1.
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1557
12.
Replace helloworld testsuite with simple testsuite that brings up EAL
via testpmd, then stops
1.
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1567
13.
Update testsuite subclass docstrings so that they all use the “Steps”
and “Verify” format for each testcase.
1.
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1599
14.
Add test case/suite context parameters, e.g. required cores
1.
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1600
15.
Continue porting the func tests on bugzilla:
1.
All func tests in progress should be tracked on this page:
https://bugs.dpdk.org/buglist.cgi?quicksearch=component%3Adts&list_id=8841
[-- Attachment #2: Type: text/html, Size: 23692 bytes --]
reply other threads:[~2024-12-12 22:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJvnSUA1gtvVyzSEqBdErYXSwRAeijj5MCOvcxPr5GF3O0ANrA@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=dts@dpdk.org \
--cc=npratte@iol.unh.edu \
--cc=thomas.wilks@arm.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).