From: Nicholas Pratte <npratte@iol.unh.edu>
To: Patrick Robb <probb@iol.unh.edu>
Cc: yoan.picchi@foss.arm.com, ian.stokes@intel.com,
stephen@networkplumber.org, Honnappa.Nagarahalli@arm.com,
luca.vizzarro@arm.com, thomas@monjalon.net,
thomas.wilks@arm.com, dmarx@iol.unh.edu,
paul.szczepanek@arm.com, dev@dpdk.org,
Alex Chapman <alex.chapman@arm.com>
Subject: Re: [PATCH v1 2/2] dts: add mtu update and jumbo frames test suite
Date: Fri, 24 Jan 2025 15:33:41 -0500 [thread overview]
Message-ID: <CAKXZ7ehr6x_UCZEfCYy479PdjHBHgpwW8ugONkR4A4Afae9gxg@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUDSyzQLNWJ4G==o5g4xm_fnynu-oa7y=DJYFoDj2N+-_g@mail.gmail.com>
Thank you for the feedback, see my comments below!
<snip>
>> + current_mtu = testpmd_shell.show_port_info(0).mtu
>> + self.verify(current_mtu is not None, "Error grabbing testpmd MTU value.")
>> + if current_mtu and (
>> + current_mtu >= STANDARD_MTU + VENDOR_AGNOSTIC_PADDING and mtu == STANDARD_MTU
>> + ):
>> + self.send_packet_and_verify(pkt_size=larger_frame_size, should_receive=True)
>
>
> I don't understand when this condition may be true - can you explain? Thanks!
I added some additional testing to Alex's MTU update tests to check
the forwarding of standard 1500 byte packets for MTU sizes greater
than 1500. Practically speaking this means that the suite will check
1500 byte packets for 2400, 4800 and 9000 byte MTU sizes. In all these
cases, packets of size 1509 should be forwarded. In the case of a 1500
byte MTU, this 1509 byte packet should be dropped.
Now the reason I decided to put these test 1500 byte packet tests in
the test suite at all is because the 'jumbo_frames' suite performs a
similar test; an MTU size of 9000 bytes is set, and standard 1500 byte
packets are checked for forwarding. The original 'mtu_update' doesn't
include this sort of testing in its test plan, but I figured I'd add
on this testing so that both MTU tests are more uniform in their
functional tests. It's a good question because this exact bit of
change in the test is what transformed this suite into an MTU test for
both '--max-pkt-len' and 'port config mtu' since each of these options
use different components of ethdev.
>
>>
>> + else:
>> + self.send_packet_and_verify(pkt_size=larger_frame_size, should_receive=False)
>> +
>> + @func_test
>> + def test_runtime_mtu_updating_and_forwarding(self) -> None:
>> + """Verify runtime MTU adjustments and assess packet forwarding behavior.
>> +
>> + Test:
>> + Start TestPMD in a paired topology.
>> + Set port MTU to 1500.
>> + Send packets of 1493, 1500 and 1509 bytes.
>
>
> I think 1493 should be 1491.
Nice one! I'll fix that.
>
>>
>> --
>> 2.47.1
>>
>
> Thanks, other than a couple questions here and in the associated patch this looks good. I can merge on Tuesday.
>
> Reviewed-by: Patrick Robb <probb@iol.unh.edu>
> Tested-by: Patrick Robb <probb@iol.unh.edu>
next prev parent reply other threads:[~2025-01-24 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 14:58 [PATCH v1 0/2] dts: " Nicholas Pratte
2025-01-17 14:58 ` [PATCH v1 1/2] dts: add fwd restart decorator to rx capabilities Nicholas Pratte
2025-01-20 1:11 ` Patrick Robb
2025-01-24 19:35 ` Nicholas Pratte
2025-01-17 14:58 ` [PATCH v1 2/2] dts: add mtu update and jumbo frames test suite Nicholas Pratte
2025-01-20 1:47 ` Patrick Robb
2025-01-24 20:33 ` Nicholas Pratte [this message]
2025-01-24 20:44 ` [PATCH v2 0/2] dts: " Nicholas Pratte
2025-01-24 20:44 ` [PATCH v2 1/2] dts: add fwd restart decorator to rx capabilities Nicholas Pratte
2025-01-24 20:44 ` [PATCH v2 2/2] dts: add mtu update and jumbo frames test suite 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=CAKXZ7ehr6x_UCZEfCYy479PdjHBHgpwW8ugONkR4A4Afae9gxg@mail.gmail.com \
--to=npratte@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=alex.chapman@arm.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=ian.stokes@intel.com \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--cc=stephen@networkplumber.org \
--cc=thomas.wilks@arm.com \
--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).