From: Patrick Robb <probb@iol.unh.edu>
To: Luca Vizzarro <luca.vizzarro@arm.com>
Cc: dev@dpdk.org, Paul.Szczepanek@arm.com, dmarx@iol.unh.edu,
abailey@iol.unh.edu, Nicholas Pratte <npratte@iol.unh.edu>
Subject: Re: [PATCH v4 1/3] dts: rework traffic generator inheritance structure
Date: Wed, 8 Oct 2025 12:34:32 -0400 [thread overview]
Message-ID: <CAJvnSUAz1CEoE6uPZUJg-cM5-7Ofi5GoLjsXCSwKtrPsRDSjMQ@mail.gmail.com> (raw)
In-Reply-To: <175992171905.88979.8170698746444654418.luca.vizzarro@arm.com>
[-- Attachment #1: Type: text/plain, Size: 1874 bytes --]
On Wed, Oct 8, 2025 at 7:45 AM Luca Vizzarro <luca.vizzarro@arm.com> wrote:
> Hi Patrick,
>
> I am assuming the move of send_packets is because we can't send
> arbitrary packets with a perf generator. I believe this should be
> explained as it's not clear why the move and it feels counterintuitive
> at first.
>
Sort of. We can send arbitrary packets with a perf generator, but there is
a particular use case for send_packet (send a small number of arbitrary
packets) and this is just "better" done by a capturing packet generator
like Scapy since it is concerned with reliability. The performance traffic
generators have a different focus (send in high volume), so in my view it
makes sense to encourage people to use a capturing traffic generator when
they want to send a small amount of arbitrary packets. If you think this
idea is okay, yes I can update the commit message. Or, I can reverse the
decision altogether if you don't think my justification is sound.
>
> On Wed, Oct 01, 2025 at 07:16:57PM +0000, Patrick Robb wrote:
> > diff --git
> a/dts/framework/testbed_model/traffic_generator/performance_traffic_generator.py
> b/dts/framework/testbed_model/traffic_generator/performance_traffic_generator.py
> > new file mode 100644
> > index 0000000000..6b23faa1a5
>
> > + def setup(self, topology: Topology) -> None:
> > + """Overrides
> :meth:`.traffic_generator.TrafficGenerator.setup`."""
> > + for port in self._tg_node.ports:
> > + self._tg_node.main_session.configure_port_mtu(2000, port)
>
> should do:
> port.configure_mtu(2000)
>
Thanks for starting a review. Do you have the hardware available to test
the patch as well? I am wondering whether my docs additions are sufficient
(I think they are, but a second opinion is always good). If you can't, I'll
ask Andrew to test it.
[-- Attachment #2: Type: text/html, Size: 2503 bytes --]
next prev parent reply other threads:[~2025-10-08 16:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 19:40 [RFC Patch v1 0/5] Add TREX Traffic Generator to DTS Framework Nicholas Pratte
2025-04-23 19:40 ` [RFC Patch v1 1/5] dts: rework config module to support perf TGs Nicholas Pratte
2025-04-23 19:40 ` [RFC Patch v1 2/5] dts: rework traffic generator inheritance structure Nicholas Pratte
2025-05-15 19:24 ` Patrick Robb
2025-05-16 19:12 ` Nicholas Pratte
2025-04-23 19:40 ` [RFC Patch v1 3/5] dts: add asychronous support to ssh sessions Nicholas Pratte
2025-05-15 19:24 ` Patrick Robb
2025-04-23 19:40 ` [RFC Patch v1 4/5] dts: add trex traffic generator to dts framework Nicholas Pratte
2025-05-15 19:25 ` Patrick Robb
2025-05-16 19:45 ` Nicholas Pratte
2025-04-23 19:40 ` [RFC Patch v1 5/5] dts: add performance test functions to test suite api Nicholas Pratte
2025-05-15 19:25 ` Patrick Robb
2025-05-16 20:18 ` [RFC v2 0/6] Add TREX Traffic Generator to DTS Framework Nicholas Pratte
2025-05-16 20:18 ` [RFC v2 1/6] dts: rework config module to support perf TGs Nicholas Pratte
2025-05-20 20:33 ` Dean Marx
2025-05-16 20:18 ` [RFC v2 2/6] dts: rework traffic generator inheritance structure Nicholas Pratte
2025-05-21 20:36 ` Dean Marx
2025-05-16 20:18 ` [RFC v2 3/6] dts: add asynchronous support to ssh sessions Nicholas Pratte
2025-05-22 15:04 ` Dean Marx
2025-05-16 20:18 ` [RFC v2 4/6] dts: add extended timeout option to interactive shells Nicholas Pratte
2025-05-22 15:10 ` Dean Marx
2025-05-16 20:18 ` [RFC v2 5/6] dts: add trex traffic generator to dts framework Nicholas Pratte
2025-05-22 16:55 ` Dean Marx
2025-05-16 20:18 ` [RFC v2 6/6] dts: add performance test functions to test suite api Nicholas Pratte
2025-05-22 17:54 ` Dean Marx
2025-07-02 5:21 ` [PATCH v3 1/5] dts: rework config module to support perf TGs Patrick Robb
2025-07-02 5:21 ` [PATCH v3 2/5] dts: rework traffic generator inheritance structure Patrick Robb
2025-07-02 15:31 ` Luca Vizzarro
2025-07-02 5:21 ` [PATCH v3 3/5] dts: add timeout override option to interactive shells Patrick Robb
2025-07-02 15:33 ` Luca Vizzarro
2025-07-02 5:21 ` [PATCH v3 4/5] dts: add trex traffic generator to dts framework Patrick Robb
2025-07-02 16:32 ` Luca Vizzarro
2025-07-02 5:21 ` [PATCH v3 5/5] dts: add performance test functions to test suite API Patrick Robb
2025-07-02 16:37 ` Luca Vizzarro
2025-07-02 15:09 ` [PATCH v3 1/5] dts: rework config module to support perf TGs Luca Vizzarro
2025-10-01 23:16 ` [PATCH v4 0/3] Add TREX Traffic Generator to DTS Framework Patrick Robb
2025-10-01 23:16 ` [PATCH v4 1/3] dts: rework traffic generator inheritance structure Patrick Robb
2025-10-08 11:45 ` Luca Vizzarro
2025-10-08 16:34 ` Patrick Robb [this message]
2025-10-01 23:16 ` [PATCH v4 2/3] dts: add trex traffic generator to dts framework Patrick Robb
2025-10-01 23:16 ` [PATCH v4 3/3] dts: add performance test functions to test suite API 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=CAJvnSUAz1CEoE6uPZUJg-cM5-7Ofi5GoLjsXCSwKtrPsRDSjMQ@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=Paul.Szczepanek@arm.com \
--cc=abailey@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=luca.vizzarro@arm.com \
--cc=npratte@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).