From: Dean Marx <dmarx@iol.unh.edu>
To: Patrick Robb <probb@iol.unh.edu>
Cc: luca.vizzarro@arm.com, yoan.picchi@foss.arm.com,
Honnappa.Nagarahalli@arm.com, paul.szczepanek@arm.com,
dev@dpdk.org
Subject: Re: [PATCH v4 3/3] dts: add virtio forwarding test suite
Date: Fri, 7 Nov 2025 16:53:30 -0500 [thread overview]
Message-ID: <CABD7UXMC+XNBcuXNrbd85mD7jANuqLrx_zYmJQECz+2URCr2jQ@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUAHYDFrZ2cEZPUxdunAe95MpQbvwpU7AUtGFK9q+XRmKA@mail.gmail.com>
On Fri, Nov 7, 2025 at 3:49 PM Patrick Robb <probb@iol.unh.edu> wrote:
>
>
>
> Is it the case that if I already have tap0 created on my SUT machine, this testsuite will create a tap1 and then the testsuite will fail to run properly on the line above (because tap1 won't be brought up)? If there is no way of getting around this limitation, we should add a new capability for "tap interface names available" or something and skip if tap0 is found in "ip a" or a similar solution.
Yes, I've added a workaround which sends a delete tap0 command prior
to the testpmd session starting. If the tap0 interface doesn't exist
it fails silently and continues with the rest of the test case.
>>
>
>
> Otherwise, change the pvp requirement to ONE_LINK, set portlist to 0, 2, 1 (2 is the vdev) when 2 link topology, and 0, 1 when 1 link, and set forwarding to chained mode so that the packet forwarding works as expected regardless of whether we have 1 or 2 physical interfaces the testpmd instance is using.
Done
>
> Thanks.
>
> Reviewed-by: Patrick Robb <probb@iol.unh.edu>
Thanks for the review!
next prev parent reply other threads:[~2025-11-07 21:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 20:04 [PATCH v1 1/2] dts: add start Tx first method to testpmd shell Dean Marx
2025-09-16 20:04 ` [PATCH v1 2/2] dts: add virtio forwarding test suite Dean Marx
2025-09-23 11:38 ` Luca Vizzarro
2025-10-03 18:14 ` Dean Marx
2025-10-09 13:04 ` Patrick Robb
2025-09-23 11:27 ` [PATCH v1 1/2] dts: add start Tx first method to testpmd shell Luca Vizzarro
2025-10-03 19:27 ` [PATCH v2 " Dean Marx
2025-10-03 19:27 ` [PATCH v2 2/2] dts: add virtio forwarding test suite Dean Marx
2025-10-21 15:13 ` Luca Vizzarro
2025-10-21 17:35 ` Dean Marx
2025-10-23 12:59 ` Patrick Robb
2025-10-24 18:38 ` Dean Marx
2025-10-24 17:46 ` [PATCH v3 1/3] dts: add start Tx first method to testpmd shell Dean Marx
2025-10-24 17:46 ` [PATCH v3 2/3] dts: add method for bringing link of interface up Dean Marx
2025-10-24 17:47 ` [PATCH v3 3/3] dts: add virtio forwarding test suite Dean Marx
2025-10-24 18:50 ` [PATCH v4 1/3] dts: add start Tx first method to testpmd shell Dean Marx
2025-10-24 18:50 ` [PATCH v4 2/3] dts: add method for bringing link of interface up Dean Marx
2025-10-24 18:50 ` [PATCH v4 3/3] dts: add virtio forwarding test suite Dean Marx
2025-11-07 20:48 ` Patrick Robb
2025-11-07 21:53 ` Dean Marx [this message]
2025-11-07 21:50 ` [PATCH v5 1/4] dts: add start Tx first method to testpmd shell Dean Marx
2025-11-07 21:50 ` [PATCH v5 2/4] dts: add methods for runtime interface config Dean Marx
2025-11-07 21:50 ` [PATCH v5 3/4] dts: add set portlist command to testpmd shell Dean Marx
2025-11-07 21:50 ` [PATCH v5 4/4] dts: add virtio forwarding test suite Dean Marx
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=CABD7UXMC+XNBcuXNrbd85mD7jANuqLrx_zYmJQECz+2URCr2jQ@mail.gmail.com \
--to=dmarx@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=luca.vizzarro@arm.com \
--cc=paul.szczepanek@arm.com \
--cc=probb@iol.unh.edu \
--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).