From: Luca Vizzarro <luca.vizzarro@arm.com>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Luca Vizzarro <luca.vizzarro@arm.com>,
Patrick Robb <probb@iol.unh.edu>,
Paul Szczepanek <paul.szczepanek@arm.com>
Subject: [PATCH v2 0/3] dts: add packet capture test suite
Date: Tue, 6 May 2025 14:29:30 +0100 [thread overview]
Message-ID: <20250506132933.1580584-1-luca.vizzarro@arm.com> (raw)
In-Reply-To: <20250331155800.449823-1-thomas.wilks@arm.com>
Hi there,
sending in a v2 for the packet capture test suite.
v2:
- added a new command to change file permissions on remote
- changed test suite to use dpdk-dumpcap instead of dpdk-pdump
Best regards,
Luca
Luca Vizzarro (1):
dts: add facility to change file permissions
Thomas Wilks (2):
dts: import lldp package in scapy
dts: add packet capture test suite
.../dts/tests.TestSuite_packet_capture.rst | 8 +
dts/framework/testbed_model/os_session.py | 34 +++
dts/framework/testbed_model/posix_session.py | 11 +-
.../testbed_model/traffic_generator/scapy.py | 1 +
dts/tests/TestSuite_packet_capture.py | 238 ++++++++++++++++++
5 files changed, 291 insertions(+), 1 deletion(-)
create mode 100644 doc/api/dts/tests.TestSuite_packet_capture.rst
create mode 100644 dts/tests/TestSuite_packet_capture.py
--
2.43.0
next prev parent reply other threads:[~2025-05-06 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 15:57 [PATCH 0/2] " Thomas Wilks
2025-03-31 15:57 ` [PATCH 1/2] " Thomas Wilks
2025-04-10 17:04 ` Dean Marx
2025-04-10 22:46 ` Stephen Hemminger
2025-03-31 15:58 ` [PATCH 2/2] dts: import lldp package in scapy Thomas Wilks
2025-04-10 17:06 ` Dean Marx
2025-05-06 13:29 ` Luca Vizzarro [this message]
2025-05-06 13:29 ` [PATCH v2 1/3] " Luca Vizzarro
2025-05-06 13:29 ` [PATCH v2 2/3] dts: add facility to change file permissions Luca Vizzarro
2025-05-06 13:29 ` [PATCH v2 3/3] dts: add packet capture test suite 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=20250506132933.1580584-1-luca.vizzarro@arm.com \
--to=luca.vizzarro@arm.com \
--cc=dev@dpdk.org \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=stephen@networkplumber.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 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).