From: "Jiale, SongX" <songx.jiale@intel.com>
To: "Ling, Jin" <jin.ling@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Peng, Yuan" <yuan.peng@intel.com>,
"Tu, Lijuan" <lijuan.tu@intel.com>,
"Ling, Jin" <jin.ling@intel.com>
Subject: RE: [DTS][PATCH V5 3/3] test_plans/ice_dcf_disable_acl_filter: add ice_dcf_disable_acl_filter test plan
Date: Wed, 14 Dec 2022 07:07:11 +0000 [thread overview]
Message-ID: <CH0PR11MB57403EF673E2637F06A65D20E7E09@CH0PR11MB5740.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221213030453.3434087-4-jin.ling@intel.com>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
> -----Original Message-----
> From: Jin Ling <jin.ling@intel.com>
> Sent: Tuesday, December 13, 2022 11:05 AM
> To: dts@dpdk.org
> Cc: Peng, Yuan <yuan.peng@intel.com>; Tu, Lijuan <lijuan.tu@intel.com>;
> Ling, Jin <jin.ling@intel.com>
> Subject: [DTS][PATCH V5 3/3] test_plans/ice_dcf_disable_acl_filter: add
> ice_dcf_disable_acl_filter test plan
>
> The startup time of ACL engine is too long, so add a devargs that customers
> can use it to disable/enable ACL engine.
> add new test plan to test if ACL engine is disabled.
>
> Signed-off-by: Jin Ling <jin.ling@intel.com>
> ---
Tested-by: Song Jiale <songx.jiale@intel.com>
[-- Attachment #2: ICEDCFACLDisableFilterTest.log --]
[-- Type: application/octet-stream, Size: 47877 bytes --]
next prev parent reply other threads:[~2022-12-14 7:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 3:04 [DTS][PATCH V5 0/3] add ice_dcf_disable_acl_filter Jin Ling
2022-12-13 3:04 ` [DTS][PATCH V5 1/3] test_plans/index.rst: add ice_dcf_disable_acl_filter test plan Jin Ling
2022-12-13 3:04 ` [DTS][PATCH V5 2/3] tests/ice_dcf_disable_acl_filter: add new test suite Jin Ling
2022-12-13 3:04 ` [DTS][PATCH V5 3/3] test_plans/ice_dcf_disable_acl_filter: add ice_dcf_disable_acl_filter test plan Jin Ling
2022-12-13 9:18 ` Peng, Yuan
2022-12-14 7:07 ` Jiale, SongX [this message]
2022-12-22 8:56 ` 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=CH0PR11MB57403EF673E2637F06A65D20E7E09@CH0PR11MB5740.namprd11.prod.outlook.com \
--to=songx.jiale@intel.com \
--cc=dts@dpdk.org \
--cc=jin.ling@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).