test suite reviews and discussions
 help / color / mirror / Atom feed
From: Ke Xu <ke1.xu@intel.com>
To: dts@dpdk.org
Cc: ke1.xu@intel.com, qi.fu@intel.com, lijuan.tu@intel.com,
	yux.jiang@intel.com, zhiminx.huang@intel.com
Subject: [DTS][PATCH V4 0/5] Update vf_offload cases for DPDK-v23.03 validation.
Date: Tue, 14 Feb 2023 14:28:35 +0800	[thread overview]
Message-ID: <20230214062840.2434213-1-ke1.xu@intel.com> (raw)

Add VLAN Packets to ensure checksum offload works well on packets with Dot1Q part.

For daily regression, we introduce wrapped cases for each path.

Updated TSO validation methods.

Ke Xu (5):
  tests/vf_offload: add VLAN packets to test scope.
  tests/vf_offload: improve TSO validating.
  tests/vf_offload: improve vector path validating.
  tests/vf_offload: fix error when no packet captured.
  test_plans/vf_offload: add VLAN packets to test scope and improve
    vector path validating.

 test_plans/vf_offload_test_plan.rst | 158 +++++
 tests/TestSuite_vf_offload.py       | 913 ++++++++++++++++++----------
 2 files changed, 762 insertions(+), 309 deletions(-)

-- 
2.25.1


             reply	other threads:[~2023-02-14  6:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14  6:28 Ke Xu [this message]
2023-02-14  6:28 ` [DTS][PATCH V4 1/5] tests/vf_offload: add VLAN packets to test scope Ke Xu
2023-02-14  6:28 ` [DTS][PATCH V4 2/5] tests/vf_offload: improve TSO validating Ke Xu
2023-02-14  6:28 ` [DTS][PATCH V4 3/5] tests/vf_offload: improve vector path validating Ke Xu
2023-02-14  6:28 ` [DTS][PATCH V4 4/5] tests/vf_offload: fix error when no packet captured Ke Xu
2023-02-14  6:28 ` [DTS][PATCH V4 5/5] test_plans/vf_offload: add VLAN packets to test scope and improve vector path validating Ke Xu

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=20230214062840.2434213-1-ke1.xu@intel.com \
    --to=ke1.xu@intel.com \
    --cc=dts@dpdk.org \
    --cc=lijuan.tu@intel.com \
    --cc=qi.fu@intel.com \
    --cc=yux.jiang@intel.com \
    --cc=zhiminx.huang@intel.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).