From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "An, XiangX" <xiangx.an@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "An, XiangX" <xiangx.an@intel.com>
Subject: Re: [dts] [PATCH V2 4/4] tests/unit_tests_eal: modify code to adapt avx512
Date: Fri, 5 Nov 2021 13:22:50 +0000 [thread overview]
Message-ID: <702b959dab0b4d98bee665091f2ba06c@intel.com> (raw)
In-Reply-To: <1636008699-16970-4-git-send-email-xiangx.an@intel.com>
> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Xiang An
> Sent: 2021年11月4日 14:52
> To: dts@dpdk.org
> Cc: An, XiangX <xiangx.an@intel.com>
> Subject: [dts] [PATCH V2 4/4] tests/unit_tests_eal: modify code to adapt avx512
>
> Modify code to adapt rxmod avx512.
>
> Signed-off-by: Xiang An <xiangx.an@intel.com>
> ---
> tests/TestSuite_unit_tests_eal.py | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/tests/TestSuite_unit_tests_eal.py b/tests/TestSuite_unit_tests_eal.py
> index 8096183..9b44132 100644
> --- a/tests/TestSuite_unit_tests_eal.py
> +++ b/tests/TestSuite_unit_tests_eal.py
> @@ -38,7 +38,7 @@ EAL autotest.
>
> import framework.utils as utils
> from framework.test_case import TestCase
> -
> +from framework.settings import load_global_setting,
> DPDK_RXMODE_SETTING
> #
> #
> # Test class.
> @@ -457,13 +457,15 @@ class TestUnitTestsEal(TestCase):
> """
> Run acl autotest.
> """
> -
> - eal_params = self.dut.create_eal_parameters()
> - self.test_app_cmdline += "--no-pci"
> + default_cores = '1S/4C/1T'
default_cores defined but not used.
prev parent reply other threads:[~2021-11-05 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-04 6:51 [dts] [PATCH V2 1/4] tests/kernelpf_iavf: " Xiang An
2021-11-04 6:51 ` [dts] [PATCH V2 2/4] tests/vf_vlan: " Xiang An
2021-11-05 12:31 ` Tu, Lijuan
2021-11-04 6:51 ` [dts] [PATCH V2 3/4] tests/l3fwdacl: " Xiang An
2021-11-05 13:24 ` Tu, Lijuan
2021-11-04 6:51 ` [dts] [PATCH V2 4/4] tests/unit_tests_eal: " Xiang An
2021-11-05 13:22 ` 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=702b959dab0b4d98bee665091f2ba06c@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@dpdk.org \
--cc=xiangx.an@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).