From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1896] DTS yaml configs updates
Date: Thu, 26 Feb 2026 00:19:02 +0000 [thread overview]
Message-ID: <bug-1896-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1896
Bug ID: 1896
Summary: DTS yaml configs updates
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: probb@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
A couple updates which I have in mind:
1. There is minimal application for the vdevs field in test_run.yaml currently.
Vdevs are coded directly into testsuites, but we are not writing testsuites
that are "vdev agnostic" such that the vdev can come in as a config value.
Pending this broader conversation regarding vdev usage in DTS, the vdev field
should be commented out by default in test_run.example.yaml.
2. Over time we have added in additional optional fields to the yaml configs,
and basically just added inline comments to each of these explaining their
usage and optional status. I fear this is potentially confusing for newcomers,
and propose that we add a multiline comment at the top of nodes.example.yaml
and test_run.example.yaml giving a full explanation for these.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-02-26 0:19 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=bug-1896-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.