From: Patrick Robb <probb@iol.unh.edu>
To: Paul.Szczepanek@arm.com
Cc: dev@dpdk.org, Luca.Vizzarro@arm.com, npratte@iol.unh.edu,
thomas.wilks@arm.com, dmarx@iol.unh.edu
Subject: Re: [PATCH 2/2] dts: add port control testing suite
Date: Thu, 24 Apr 2025 08:08:14 -0400 [thread overview]
Message-ID: <CAJvnSUDUQ7Hi6zmwyqTdL2A4ZNdbL11OeTkW=O2cag+7q2-6vQ@mail.gmail.com> (raw)
In-Reply-To: <20250424014412.3849896-3-probb@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On Wed, Apr 23, 2025 at 9:48 PM Patrick Robb <probb@iol.unh.edu> wrote:
> From: Jeremy Spewock <jspewock@iol.unh.edu>
>
Should add:
@requires(topology_type=TopologyType.two_links)
> +class TestPortControl(TestSuite):
> + """DPDK Port Control Testing Suite."""
> +
> + def send_packets_and_verify(self) -> None:
> + """Send 100 packets and verify that all packets were forwarded
> back.
> +
> + Packets sent are identical and are all ethernet frames with a
> payload of 30 "X" characters.
> + This payload is used to differentiate noise on the wire from
> packets sent by this
> + framework.
>
>
[-- Attachment #2: Type: text/html, Size: 1276 bytes --]
prev parent reply other threads:[~2025-04-24 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-14 18:20 [PATCH v1 0/2] dts: port over port_control " jspewock
2024-08-14 18:20 ` [PATCH v1 1/2] dts: add methods for closing ports to testpmd jspewock
2024-08-14 18:20 ` [PATCH v1 2/2] dts: add port control testing suite jspewock
2024-09-23 16:44 ` [PATCH v2 0/2] dts: port over port_control " jspewock
2024-09-23 16:44 ` [PATCH v2 1/2] dts: add method for closing ports to testpmd jspewock
2024-09-23 16:44 ` [PATCH v2 2/2] dts: add port control testing suite jspewock
2025-04-24 1:44 ` [PATCH 0/2] dts: port over port_control " Patrick Robb
2025-04-24 1:44 ` [PATCH 1/2] dts: add method for closing ports to testpmd Patrick Robb
2025-04-24 1:44 ` [PATCH 2/2] dts: add port control testing suite Patrick Robb
2025-04-24 12:08 ` Patrick Robb [this message]
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='CAJvnSUDUQ7Hi6zmwyqTdL2A4ZNdbL11OeTkW=O2cag+7q2-6vQ@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=npratte@iol.unh.edu \
--cc=thomas.wilks@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;
as well as URLs for NNTP newsgroup(s).