test suite reviews and discussions
 help / color / mirror / Atom feed
From: Ke Xu <ke1.xu@intel.com>
To: dts@dpdk.org
Cc: lijuan.tu@intel.com, yuan.peng@intel.com, ke1.xu@intel.com
Subject: [DTS][PATCH V3 0/3] add packets count, super-long packets and random payload to the case
Date: Wed,  4 Jan 2023 15:20:50 +0800	[thread overview]
Message-ID: <20230104072053.86366-1-ke1.xu@intel.com> (raw)

Long packet and repeating packet sending helps triggering potential failures.
 For example, in DPDK 20.11 there was an MDD problem when handling long
 packets with TSO enabled.

This patch implemented packets count that sends multiple packets of one
 packet combination to trigger problems only happen under massive packets
 received. This patch also implemented random payload.

This patch added super-long packet of payload length of 8500. This helps
 triggering potential issues of ex-limit input.

Ke Xu (3):
  test_plans/vf_offload: fix wrong example packets.
  test_plans/vf_offload: add packets count, super-long packets and
    random payload to the case.
  tests/vf_offload: implement packets count, super-long packet and
    random payload.

 test_plans/vf_offload_test_plan.rst | 155 +++++++++++++++-------------
 tests/TestSuite_vf_offload.py       | 150 ++++++++++++++++++++++-----
 2 files changed, 206 insertions(+), 99 deletions(-)

-- 
2.25.1


             reply	other threads:[~2023-01-04  7:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  7:20 Ke Xu [this message]
2023-01-04  7:20 ` [DTS][PATCH V3 1/3] test_plans/vf_offload: fix wrong example packets Ke Xu
2023-01-04  7:20 ` [DTS][PATCH V3 2/3] test_plans/vf_offload: add packets count, super-long packets and random payload to the case Ke Xu
2023-01-04  7:20 ` [DTS][PATCH V3 3/3] tests/vf_offload: implement packets count, super-long packet and random payload Ke Xu
2023-01-05  7:11   ` Peng, Yuan
2023-01-05 14:26   ` lijuan.tu

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=20230104072053.86366-1-ke1.xu@intel.com \
    --to=ke1.xu@intel.com \
    --cc=dts@dpdk.org \
    --cc=lijuan.tu@intel.com \
    --cc=yuan.peng@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).