On Mon, May 20, 2024 at 1:56 PM Luca Vizzarro <luca.vizza...@arm.com> wrote: > > On 14/05/2024 21:14, jspew...@iol.unh.edu wrote: > > + # adjust the MTU of the SUT ports > > + testpmd.set_port_mtu(0, 9000) > > + testpmd.set_port_mtu(1, 9000) > > should you perhaps do this for every port in the testpmd shell instead? > > for port_id in range(testpmd.number_of_ports): > testpmd.set_port_mtu(port_id, 9000)
This is a good thought. I was sort of falling back on the current assumption that we can only support 2 ports per server in test suites, but there is nothing that ensures these ports are the first and second in trestpmd. I think it is probably safer to just modify the MTU of all ports that testpmd knows of since we just blindly pick the ingress and egress ports we want to use. I didn't want to at first since the ideal would be that we have minimal side effects in testing suites so we wouldn't want to just change the MTU of all ports, but if there comes a time when this matters in the future (the only one I could really think of is implementing parallel testing) then we can just limit what ports are in the scope of testpmd. > > > testpmd.stop() > > + # reset the MTU of the SUT ports > > + testpmd.set_port_mtu(0, 1500) > > + testpmd.set_port_mtu(1, 1500) > > As above >
