From: Luca Vizzarro <Luca.Vizzarro@arm.com>
To: Jeremy Spewock <jspewock@iol.unh.edu>
Cc: dev@dpdk.org, "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:44:02 +0100 [thread overview]
Message-ID: <c8ac467a-a051-444d-ae5d-148b41b2c457@arm.com> (raw)
In-Reply-To: <CAAA20US52rQfWKRjy0rdgjLJx8WxEbY7Kq=nTA-SaBcA9jBRPw@mail.gmail.com>
On 09/08/2024 16:27, Jeremy Spewock wrote:
>> Signed-off-by: Luca Vizzarro <luca.vizzarro@arm.com>
>> Reviewed-by: Paul Szczepanek <paul.szczepanek@arm.com>
>> ---
>> Depends-on: series-32714 ("dts: add pktgen and testpmd changes")
>
> Out of my own curiosity, are depends on supposed to be outside of the
> commit body? I don't think it really matters for automation or
> anything regardless, but I just didn't know if there was a rule about
> it.
Depends-on tags are metadata for Patchwork, they don't belong in the
repository. So there shouldn't be any depends-on committed as it
wouldn't make any sense in Git. My reply aside, the contributing
guidelines also specify how to do it[1].
>> new file mode 100644
>> index 0000000000..46f07b78eb
>> --- /dev/null
>> +++ b/dts/tests/TestSuite_l2fwd.py
>> @@ -0,0 +1,58 @@
>
> This file looks like it is missing the copyright information at the top.
Argh! Good catch, thank you!
>> +"""Basic L2 forwarding test suite.
>> +
>> +This testing suites runs basic L2 forwarding on testpmd with different queue sizes per port.
>
> The phrasing of "different queue sizes per port" makes me initially
> think that like, port 0 will have 2 queues and port 1 will have 4.
> Maybe something like "This testing suites runs basic L2 forwarding on
> testpmd across multiple different queue sizes" would make this more
> clear.
>
Ack.
>> + def set_up_suite(self) -> None:
>> + """Set up the test suite.
>> +
>> + Setup:
>> + Verify that we have at least 2 ports in the current test. Generate the random packets
>> + that will be sent and spawn a reusable testpmd shell.
>
> Seems like this method is no longer spawning a testpmd shell, so this
> part of the doc-string is no longer relevant.
Ack. Remnants of an earlier version... :')
>> + 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
>
> It might make sense to name the numbers of queues in the doc-string
> just so that the rst for the suite is more clear.
Ack.
>> + expected_packets = [self.get_expected_packet(packet) for packet in self.packets]
>
> Ahh, the get_expected_packet method also sheds some light on how the
> match_all_packets could be useful.
>
:)
[1] https://doc.dpdk.org/guides/contributing/patches.html#patch-dependencies
next prev parent reply other threads:[~2024-09-09 10:44 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 [this message]
2024-09-04 18:11 ` Dean Marx
2024-09-09 15:05 ` Patrick Robb
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=c8ac467a-a051-444d-ae5d-148b41b2c457@arm.com \
--to=luca.vizzarro@arm.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=jspewock@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--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).