From: Patrick Robb <probb@iol.unh.edu>
To: Dean Marx <dmarx@iol.unh.edu>, Nicholas Pratte <npratte@iol.unh.edu>
Cc: Luca Vizzarro <Luca.Vizzarro@arm.com>,
Paul Szczepanek <Paul.Szczepanek@arm.com>, dev <dev@dpdk.org>
Subject: Ethertype and Rx/Tx offload suites - collaborate with Luca
Date: Thu, 6 Mar 2025 13:52:58 -0500 [thread overview]
Message-ID: <CAJvnSUCwRgakHWimtK2hjsmF__RKkgRSc5wK-ZyJ6kSp04ddcg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
Hi Dean/Nick,
Luca said this morning he is starting to look at Ethertype and rx/tx
offload testsuites. At the CI meeting I gave him an overview of what you
both had learned about these so there isn't double work. My summary:
Ethertype:
1.TPID/VLAN filtering works only on Mellanox NICs and we don't know why so
we are blocked pending this ticket:
https://bugs.dpdk.org/show_bug.cgi?id=1464
2. Nick I mentioned how you were looking at Intel's offering of supporting
non-standard TPIDs and how this was not done by other vendors, and raised
the decision of supporting these testcases, or scoping the testsuite down
to only standard TPIDs.
3.If you can share your patch files with Luca and describe where you landed
with the device capability check for this it may prevent double work.
rx/tx offload:
1.Dean has rebased this series but is running into a bug with the
capability check test parser returning no flags. He confirmed from running
the steps manually that the flags we expect are being reported by testpmd.
2. Dean please provide a summary to Luca so there is no double work.
Thanks guys.
[-- Attachment #2: Type: text/html, Size: 1432 bytes --]
next reply other threads:[~2025-03-06 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 18:52 Patrick Robb [this message]
2025-03-06 22:06 ` 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=CAJvnSUCwRgakHWimtK2hjsmF__RKkgRSc5wK-ZyJ6kSp04ddcg@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=npratte@iol.unh.edu \
/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).