From: Patrick Robb <probb@iol.unh.edu>
To: Luca Vizzarro <luca.vizzarro@arm.com>
Cc: dev@dpdk.org, "Jeremy Spewock" <jspewock@iol.unh.edu>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
"Paul Szczepanek" <paul.szczepanek@arm.com>
Subject: Re: [PATCH] dts: add l2fwd test suite
Date: Mon, 9 Sep 2024 11:05:38 -0400 [thread overview]
Message-ID: <CAJvnSUB2y=vc5LRW1pv7zYtQPy=8+ZgnT_2HMZUjHSj08w-uVg@mail.gmail.com> (raw)
In-Reply-To: <20240806125140.2582859-1-luca.vizzarro@arm.com>
Reviewed-by: Patrick Robb <probb@iol.unh.edu>
Tested-by: Patrick Robb <probb@iol.unh.edu>
Ran on a Broadcom 57414 2x25G NIC on an Intel x86 server.
I'll follow up with a review on the pktgen and testpmd changes series
as obviously we want to move that to next-dts. Thanks!
On Tue, Aug 6, 2024 at 8:53 AM Luca Vizzarro <luca.vizzarro@arm.com> wrote:
> + def test_l2fwd_integrity(self) -> None:
> + """Test the L2 forwarding integrity.
> +
> + Test:
> + Configure a testpmd shell with a different numbers of queues per run. Start up L2
> + forwarding, send random packets from the TG and verify they were all received back.
> + """
> + queues = [1, 2, 4, 8]
The only question I had was whether we need a show port info
capability check to verify the max queues per port is at least 8, but
I think that 8 is so low that we will not realistically run into this
problem, after a quick 60 second check on a couple NICs.
next prev parent reply other threads:[~2024-09-09 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 12:51 Luca Vizzarro
2024-08-09 15:27 ` Jeremy Spewock
2024-09-09 10:44 ` Luca Vizzarro
2024-09-04 18:11 ` Dean Marx
2024-09-09 15:05 ` Patrick Robb [this message]
2024-09-09 17:54 ` Nicholas Pratte
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='CAJvnSUB2y=vc5LRW1pv7zYtQPy=8+ZgnT_2HMZUjHSj08w-uVg@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@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).