From: Luca Vizzarro <luca.vizzarro@arm.com>
To: dev@dpdk.org
Cc: Luca Vizzarro <luca.vizzarro@arm.com>,
Patrick Robb <probb@iol.unh.edu>,
Paul Szczepanek <paul.szczepanek@arm.com>
Subject: [PATCH v2 0/7] dts: shell improvements
Date: Fri, 14 Mar 2025 15:18:50 +0200 [thread overview]
Message-ID: <20250314131857.1298247-1-luca.vizzarro@arm.com> (raw)
In-Reply-To: <20241220172337.2194523-1-luca.vizzarro@arm.com>
Hi there,
sending in a v2, which should also remove the RFC status from v1, as I
believe these changes are now ready as they are.
v2:
- rebased
- added further improvements
- reworked shell registration based on the recent framework
improvements, e.g. context
- removed multi inheritance to simplify
- added a new pseudo-shell to handle blocking applications
Best,
Luca
Luca Vizzarro (7):
dts: escape single quotes
dts: add blocking dpdk app class
dts: add shells pool
dts: revert back to a single InteractiveShell
dts: make shells path dynamic
dts: remove multi-inheritance classes
dts: enable shell pooling
doc/api/dts/framework.remote_session.rst | 1 +
.../framework.remote_session.shell_pool.rst | 8 +
dts/framework/context.py | 2 +
dts/framework/remote_session/dpdk_app.py | 80 +++++
dts/framework/remote_session/dpdk_shell.py | 21 +-
.../remote_session/interactive_shell.py | 302 ++++++++++++++++--
dts/framework/remote_session/python_shell.py | 13 +-
dts/framework/remote_session/shell_pool.py | 106 ++++++
.../single_active_interactive_shell.py | 269 ----------------
dts/framework/remote_session/testpmd_shell.py | 16 +-
dts/framework/test_run.py | 5 +
dts/framework/testbed_model/linux_session.py | 1 +
.../testbed_model/traffic_generator/scapy.py | 38 ++-
.../traffic_generator/traffic_generator.py | 6 +-
dts/framework/utils.py | 14 -
15 files changed, 531 insertions(+), 351 deletions(-)
create mode 100644 doc/api/dts/framework.remote_session.shell_pool.rst
create mode 100644 dts/framework/remote_session/dpdk_app.py
create mode 100644 dts/framework/remote_session/shell_pool.py
delete mode 100644 dts/framework/remote_session/single_active_interactive_shell.py
--
2.43.0
next prev parent reply other threads:[~2025-03-14 13:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 17:23 [RFC PATCH 0/2] dts: add basic scope to improve shell handling Luca Vizzarro
2024-12-20 17:24 ` [RFC PATCH 1/2] dts: add scoping and shell registration to Node Luca Vizzarro
2024-12-20 17:24 ` [RFC PATCH 2/2] dts: revert back shell split Luca Vizzarro
2025-03-14 13:18 ` Luca Vizzarro [this message]
2025-03-14 13:18 ` [PATCH v2 1/7] dts: escape single quotes Luca Vizzarro
2025-03-14 13:18 ` [PATCH v2 2/7] dts: add blocking dpdk app class Luca Vizzarro
2025-03-14 13:18 ` [PATCH v2 3/7] dts: add shells pool Luca Vizzarro
2025-03-14 13:18 ` [PATCH v2 4/7] dts: revert back to a single InteractiveShell Luca Vizzarro
2025-03-14 13:18 ` [PATCH v2 5/7] dts: make shells path dynamic Luca Vizzarro
2025-03-14 13:18 ` [PATCH v2 6/7] dts: remove multi-inheritance classes Luca Vizzarro
2025-03-14 13:18 ` [PATCH v2 7/7] dts: enable shell pooling Luca Vizzarro
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=20250314131857.1298247-1-luca.vizzarro@arm.com \
--to=luca.vizzarro@arm.com \
--cc=dev@dpdk.org \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
/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).