From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Khangar, Churchill" <churchill.khangar@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"P, Venkata Suresh Kumar" <venkata.suresh.kumar.p@intel.com>,
"Khangar, Churchill" <churchill.khangar@intel.com>,
"Jangra, Yogesh" <yogesh.jangra@intel.com>
Subject: Re: [dts] [PATCH 0/2] add pipeline new features test scenarios
Date: Thu, 29 Apr 2021 08:56:10 +0000 [thread overview]
Message-ID: <e624a6c016464fe291fd23e2e94992aa@intel.com> (raw)
In-Reply-To: <1619000234-46133-1-git-send-email-churchill.khangar@intel.com>
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Churchill Khangar
> Sent: 2021年4月21日 18:17
> To: dts@dpdk.org
> Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; P, Venkata Suresh
> Kumar <venkata.suresh.kumar.p@intel.com>; Khangar, Churchill
> <churchill.khangar@intel.com>; Jangra, Yogesh <yogesh.jangra@intel.com>
> Subject: [dts] [PATCH 0/2] add pipeline new features test scenarios
>
> This patch series has the changes to support test suite for pipeline application
> new features. Also changes to improve existing test cases logic to cover
> different operand lengths, endianness issues and additional test cases for
> existing features.
>
> Following are the details of new features and existing test cases enhancements
> 1. Framework enhancements to improve overall execution time.
> 2. RING I/O port type
> 3. WCM table match
> 4. Register Array
> 5. trTCM
> 6. Enhancement to existing test cases to verify
> a. Endianness issue
> b. Operands with variable size values
> 7. Additional tests to provide more coverage for table match and actions
> 8. Additional tests to cover customer common use cases
>
> Patch details
> 1. Patch1 - pipeline dependencies archive and compressed
> file pipeline.tar.gz modified for all new features.
> 2. Patch2 - add new features test coverage.
>
> Churchill Khangar (2):
> dep: add pipeline test suite new feature dependencies
> tests/pipeline: add new features test coverage
>
> dep/pipeline.tar.gz | Bin 49082 -> 74543 bytes
> tests/TestSuite_pipeline.py | 8416 +++++++++++++++++++------------------------
> 2 files changed, 3661 insertions(+), 4755 deletions(-)
>
> --
> 1.8.3.1
Applied the series, thanks
prev parent reply other threads:[~2021-04-29 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 10:17 Churchill Khangar
2021-04-21 10:17 ` [dts] [PATCH 1/2] dep: add pipeline test suite new feature dependencies Churchill Khangar
2021-04-21 10:17 ` [dts] [PATCH 2/2] tests/pipeline: add new features test coverage Churchill Khangar
2021-04-29 8:56 ` Tu, Lijuan [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=e624a6c016464fe291fd23e2e94992aa@intel.com \
--to=lijuan.tu@intel.com \
--cc=churchill.khangar@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dts@dpdk.org \
--cc=venkata.suresh.kumar.p@intel.com \
--cc=yogesh.jangra@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).