From: Luca Vizzarro <Luca.Vizzarro@arm.com>
To: "Etelson, Gregory" <getelson@nvidia.com>,
"Thomas Monjalon" <thomas@monjalon.net>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
"Paul Szczepanek" <Paul.Szczepanek@arm.com>,
"Yoan Picchi" <yoan.picchi@foss.arm.com>,
"Jeremy Spewock" <jspewock@iol.unh.edu>,
"Patrick Robb" <probb@iol.unh.edu>, "ci@dpdk.org" <ci@dpdk.org>,
dev@dpdk.org
Subject: Re: DTS testpmd and SCAPY integration
Date: Mon, 8 Jan 2024 12:10:18 +0000 [thread overview]
Message-ID: <8dc41944-3ee6-48d0-b1e6-ff086e97aa12@arm.com> (raw)
In-Reply-To: <2a287ee7-cda4-f2ab-a4e6-a47021f8573f@nvidia.com>
Hi Gregory,
Your proposal sounds rather interesting. Certainly enabling DTS to
accept YAML-written tests sounds more developer-friendly and should
enable quicker test-writing. As this is an extra feature though – and a
nice-to-have, it should definitely be discussed in the DTS meetings as
Honnappa suggested already.
Another thing, I am not sure that the intention is that Scapy will be
the only traffic generator supported. Could be very wrong here. In the
case we'd support others too, how would you tackle this problem? We can
discuss this in the meeting as well if needed.
Best,
Luca
next prev parent reply other threads:[~2024-01-08 12:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-26 7:31 Etelson, Gregory
2024-01-08 1:55 ` Honnappa Nagarahalli
2024-01-08 6:10 ` Etelson, Gregory
2024-01-08 17:36 ` Honnappa Nagarahalli
2024-01-18 12:32 ` Juraj Linkeš
2024-01-19 20:01 ` Patrick Robb
2024-01-08 12:17 ` Luca Vizzarro
2024-01-08 17:35 ` Honnappa Nagarahalli
2024-01-08 12:10 ` Luca Vizzarro [this message]
2024-01-08 17:23 ` Etelson, Gregory
2024-01-22 17:31 ` Thomas Monjalon
2024-01-23 3:42 ` Honnappa Nagarahalli
2024-01-23 8:50 ` Thomas Monjalon
2024-01-23 18:26 ` Jeremy Spewock
2024-01-28 13:44 ` Gregory Etelson
2024-01-30 22:03 ` Patrick Robb
2024-01-31 7:42 ` Etelson, Gregory
2024-02-14 17:27 ` Gregory Etelson
2024-02-19 5:08 ` Patrick Robb
2024-02-20 13:35 ` Gregory Etelson
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=8dc41944-3ee6-48d0-b1e6-ff086e97aa12@arm.com \
--to=luca.vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=probb@iol.unh.edu \
--cc=thomas@monjalon.net \
--cc=yoan.picchi@foss.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).