From: Patrick Robb <probb@iol.unh.edu>
To: "Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Paul Szczepanek" <Paul.Szczepanek@arm.com>,
"Luca Vizzarro" <Luca.Vizzarro@arm.com>
Cc: dts@dpdk.org, ci@dpdk.org
Subject: Proposal for 24.07 DTS Roadmap
Date: Wed, 13 Mar 2024 11:44:36 -0400 [thread overview]
Message-ID: <CAJvnSUC9Nn4ieswoSQNV5qDuocaryRV5actdC-9QHjauBsxAtQ@mail.gmail.com> (raw)
Hi Honnappa,
Since we didn't sync this morning at DTS meeting, I wanted to share
the current proposed 24.07 roadmap with you. I think we can
asynchronously look it over and approve it. Or, if you want to discuss
more in depth, maybe the DPDK CI meeting next week is an appropriate
venue.
1) Write ethdev testsuites:
Jumboframes: https://git.dpdk.org/tools/dts/tree/test_plans/jumboframes_test_plan.rst
Mac Filter: https://git.dpdk.org/tools/dts/tree/test_plans/mac_filter_test_plan.rst
Dynamic Queue: https://git.dpdk.org/tools/dts/tree/test_plans/dynamic_queue_test_plan.rst
2)
Replace XMLRPC server with Scapy interactive shell:
https://bugs.dpdk.org/show_bug.cgi?id=1374
3)
Configuration schema updates:
Extend hugepage configuration options to allow for different sizes:
https://bugs.dpdk.org/show_bug.cgi?id=1370
Cut down total configuration options in schema (not all we originally
added are needed): https://bugs.dpdk.org/show_bug.cgi?id=1360
Split testbed and test configuration to different files:
https://bugs.dpdk.org/show_bug.cgi?id=1344
4)API Docs generation:
https://patchwork.dpdk.org/project/dpdk/list/?series=30877
5)Skip test cases based on testbed capabilities:
https://patches.dpdk.org/project/dpdk/patch/20240301155416.96960-1-juraj.linkes@pantheon.tech/
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1351
6)Rename the execution section/stage:
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1355
7)Add support for externally compiled DPDK:
Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=136
reply other threads:[~2024-03-13 15:44 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=CAJvnSUC9Nn4ieswoSQNV5qDuocaryRV5actdC-9QHjauBsxAtQ@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=ci@dpdk.org \
--cc=dts@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=juraj.linkes@pantheon.tech \
/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).