test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Fu, Qi" <qi.fu@intel.com>
To: "Xu, Ke1" <ke1.xu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Tu, Lijuan" <lijuan.tu@intel.com>, "Peng, Yuan" <yuan.peng@intel.com>
Subject: RE: [DTS][PATCH V2 0/3] add packets count, super-long packets and random payload to the case
Date: Mon, 26 Dec 2022 01:54:43 +0000	[thread overview]
Message-ID: <DM6PR11MB4611BBAC9700A0EE42593DFFEAEC9@DM6PR11MB4611.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221223010242.282584-1-ke1.xu@intel.com>

Acked-by: Fu, Qi <qi.fu@intel.com>

> -----Original Message-----
> From: Xu, Ke1 <ke1.xu@intel.com>
> Sent: Friday, December 23, 2022 9:03 AM
> To: dts@dpdk.org
> Cc: Tu, Lijuan <lijuan.tu@intel.com>; Fu, Qi <qi.fu@intel.com>; Peng, Yuan
> <yuan.peng@intel.com>; Xu, Ke1 <ke1.xu@intel.com>
> Subject: [DTS][PATCH V2 0/3] add packets count, super-long packets and
> random payload to the case
> 
> 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       |  66 +++++++-----
>  2 files changed, 122 insertions(+), 99 deletions(-)
> 
> --
> 2.25.1


      parent reply	other threads:[~2022-12-26  1:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-23  1:02 Ke Xu
2022-12-23  1:02 ` [DTS][PATCH V2 1/3] test_plans/vf_offload: fix wrong example packets Ke Xu
2022-12-23  1:02 ` [DTS][PATCH V2 2/3] test_plans/vf_offload: add packets count, super-long packets and random payload to the case Ke Xu
2022-12-23  1:02 ` [DTS][PATCH V2 3/3] tests/vf_offload: implement packets count, super-long packet and random payload Ke Xu
2022-12-26  1:54 ` Fu, Qi [this message]

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=DM6PR11MB4611BBAC9700A0EE42593DFFEAEC9@DM6PR11MB4611.namprd11.prod.outlook.com \
    --to=qi.fu@intel.com \
    --cc=dts@dpdk.org \
    --cc=ke1.xu@intel.com \
    --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).