From: Jeremy Spewock <jspewock@iol.unh.edu>
To: Dean Marx <dmarx@iol.unh.edu>
Cc: probb@iol.unh.edu, npratte@iol.unh.edu, luca.vizzarro@arm.com,
yoan.picchi@foss.arm.com, Honnappa.Nagarahalli@arm.com,
paul.szczepanek@arm.com, juraj.linkes@pantheon.tech,
dev@dpdk.org
Subject: Re: [PATCH v2 0/2] dts: port over checksum offload suite
Date: Fri, 23 Aug 2024 10:53:56 -0400 [thread overview]
Message-ID: <CAAA20UTvrX7ChbmY4iuRO=3LpyczPVa8vDUKaSaBSDszF_bRcA@mail.gmail.com> (raw)
In-Reply-To: <20240821162550.1163-1-dmarx@iol.unh.edu>
Hey Dean,
Thanks for the series! Looks good to me in general, I just left some
comments with a few thoughts I had about some ways to potentially move
some stuff around or swap implementations, but the functionality all
looks good to me. Let me know what you think!
Thanks,
Jeremy
On Wed, Aug 21, 2024 at 12:25 PM Dean Marx <dmarx@iol.unh.edu> wrote:
>
> -------
> v2:
> * added filter for verbose output using dst mac address
>
> Dean Marx (2):
> dts: add csum HW offload to testpmd shell
> dts: checksum offload test suite
>
> dts/framework/config/conf_yaml_schema.json | 3 +-
> dts/framework/remote_session/testpmd_shell.py | 124 ++++++++
> dts/tests/TestSuite_checksum_offload.py | 264 ++++++++++++++++++
> 3 files changed, 390 insertions(+), 1 deletion(-)
> create mode 100644 dts/tests/TestSuite_checksum_offload.py
>
> --
> 2.44.0
>
next prev parent reply other threads:[~2024-08-23 14:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 14:20 [PATCH v1 " Dean Marx
2024-08-16 14:20 ` [PATCH v1 1/2] dts: add csum HW offload to testpmd shell Dean Marx
2024-08-16 14:20 ` [PATCH v1 2/2] dts: checksum offload test suite Dean Marx
2024-08-19 14:28 ` Alex Chapman
2024-08-19 17:01 ` Dean Marx
2024-08-19 14:28 ` [PATCH v1 0/2] dts: port over checksum offload suite Alex Chapman
2024-08-19 17:02 ` Dean Marx
2024-08-21 16:25 ` [PATCH v2 " Dean Marx
2024-08-21 16:25 ` [PATCH v2 1/2] dts: add csum HW offload to testpmd shell Dean Marx
2024-08-23 14:53 ` Jeremy Spewock
2024-08-26 21:04 ` Dean Marx
2024-08-21 16:25 ` [PATCH v2 2/2] dts: checksum offload test suite Dean Marx
2024-08-23 14:54 ` Jeremy Spewock
2024-08-26 21:17 ` Dean Marx
2024-08-23 14:53 ` Jeremy Spewock [this message]
2024-08-26 21:22 ` [PATCH v3 0/2] dts: port over checksum offload suite Dean Marx
2024-08-26 21:22 ` [PATCH v3 1/2] dts: add csum HW offload to testpmd shell Dean Marx
2024-09-04 21:18 ` Jeremy Spewock
2024-08-26 21:22 ` [PATCH v3 2/2] dts: checksum offload test suite Dean Marx
2024-09-04 21:18 ` Jeremy Spewock
2024-10-14 18:23 ` [PATCH v4 0/2] dts: port over checksum offload suite Dean Marx
2024-10-14 18:23 ` [PATCH v4 1/2] dts: add csum HW offload to testpmd shell Dean Marx
2024-10-14 18:23 ` [PATCH v4 2/2] dts: checksum offload test suite Dean Marx
2024-10-15 19:13 ` [PATCH v5 0/2] dts: port over checksum offload suite Dean Marx
2024-10-15 19:13 ` [PATCH v5 1/2] dts: add csum HW offload to testpmd shell Dean Marx
2024-11-19 16:07 ` Patrick Robb
2024-11-19 16:31 ` Patrick Robb
2024-10-15 19:13 ` [PATCH v5 2/2] dts: checksum offload test suite Dean Marx
2024-11-19 16:11 ` Patrick Robb
2024-11-19 16:30 ` Patrick Robb
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='CAAA20UTvrX7ChbmY4iuRO=3LpyczPVa8vDUKaSaBSDszF_bRcA@mail.gmail.com' \
--to=jspewock@iol.unh.edu \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--cc=luca.vizzarro@arm.com \
--cc=npratte@iol.unh.edu \
--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).