From: Patrick Robb <probb@iol.unh.edu>
To: luca.vizzarro@arm.com
Cc: dev@dpdk.org, abailey@iol.unh.edu, dmarx@iol.unh.edu,
Patrick Robb <probb@iol.unh.edu>
Subject: [PATCH v2 0/2] dts: dpdk shell bug fixes
Date: Mon, 23 Mar 2026 16:20:51 -0400 [thread overview]
Message-ID: <20260323202053.740203-1-probb@iol.unh.edu> (raw)
In-Reply-To: <20260323180818.674041-1-probb@iol.unh.edu>
Support for the dpdk-test-crypto-perf application in DTS was added
recently. This work introduced a new bug (incorrectly setting the EAL
port allowlist when checking ethdev capabilities) and also exposed a
pre-existing bug (insuffient time delay between dpdk app runs causing
resource conflicts). Both of these bugs are resolved by the patches in
this series. The patches are very small, but also important for the DTS
user experience, so if there is time for these to be merged in for RC3 I
think it would be a big benefit. Thanks.
v2:
Adding missing only_active decorator to the DPDKShell close method,
which resolves a doc build issue.
Patrick Robb (2):
dts: always use ethdev ports to check capabilities
dts: avoid dpdk resources conflict
dts/api/testpmd/__init__.py | 2 +-
dts/framework/remote_session/dpdk_shell.py | 17 ++++++++++++-----
dts/framework/testbed_model/capability.py | 2 +-
3 files changed, 14 insertions(+), 7 deletions(-)
--
2.49.0
next prev parent reply other threads:[~2026-03-23 20:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 18:08 [PATCH v1 0/2] dts: dpdk shell bug fixes Patrick Robb
2026-03-23 18:08 ` [PATCH v1 1/2] dts: always use ethdev ports to check capabilities Patrick Robb
2026-03-23 19:14 ` Andrew Bailey
2026-03-23 18:08 ` [PATCH v1 2/2] dts: avoid dpdk resources conflict Patrick Robb
2026-03-23 19:15 ` Andrew Bailey
2026-03-23 19:24 ` Andrew Bailey
2026-03-23 20:20 ` Patrick Robb [this message]
2026-03-23 20:20 ` [PATCH v2 1/2] dts: always use ethdev ports to check capabilities Patrick Robb
2026-03-23 20:20 ` [PATCH v2 2/2] dts: avoid dpdk resources conflict Patrick Robb
2026-03-24 0:52 ` [PATCH v3 1/2] dts: always use ethdev ports to check capabilities Patrick Robb
2026-03-24 0:52 ` [PATCH v3 2/2] dts: avoid dpdk resources conflict Patrick Robb
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=20260323202053.740203-1-probb@iol.unh.edu \
--to=probb@iol.unh.edu \
--cc=abailey@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=luca.vizzarro@arm.com \
/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