From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"Sikora, ZbigniewX" <zbigniewx.sikora@intel.com>
Subject: Re: [dts] [PATCH] dts: introduce new test-cases for DPDK acl library
Date: Wed, 26 May 2021 08:40:16 +0000 [thread overview]
Message-ID: <fc42792690bd4c9482fccccf17702d38@intel.com> (raw)
In-Reply-To: <20210520103016.20917-1-konstantin.ananyev@intel.com>
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Konstantin Ananyev
> Sent: 2021年5月20日 18:30
> To: dts@dpdk.org
> Cc: Ananyev, Konstantin <konstantin.ananyev@intel.com>; Sikora, ZbigniewX
> <zbigniewx.sikora@intel.com>
> Subject: [dts] [PATCH] dts: introduce new test-cases for DPDK acl library
>
> Introduce new test-cases for acl library.
> Several test-cases to validate different classify algorithms:
> scalar, sse, avx2, avx512x16, avx512x32.
> DPDK test-acl app and script are main vehicles for these tests.
> These tests use pre-generated (by classbench) input rule and trace files.
>
> Signed-off-by: Zbigniew Sikora <zbigniewx.sikora@intel.com>
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> ---
> Depends-on: dpdk series-17015 ("app/acl: add script for automate testing")
> ---
> dep/test-acl-input.tar.gz | Bin 0 -> 4418039 bytes
> test_plans/acl_test_plan.rst | 183 +++++++++++++++++++++++++++++++++++
> tests/TestSuite_acl.py | 125 ++++++++++++++++++++++++
> 3 files changed, 308 insertions(+)
Could you please split the big dependence file to another patch next time ? it's really difficult to review.
next prev parent reply other threads:[~2021-05-26 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 10:30 Konstantin Ananyev
2021-05-26 8:40 ` Tu, Lijuan [this message]
2021-05-26 9:37 ` Ananyev, Konstantin
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=fc42792690bd4c9482fccccf17702d38@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=zbigniewx.sikora@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).