From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "nareddy@marvell.com" <nareddy@marvell.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "fmasood@marvell.com" <fmasood@marvell.com>,
"avijay@marvell.com" <avijay@marvell.com>
Subject: Re: [dts] [PATCH] TestSuite_pmdrssreta.py: Modified rss ket size for cavium_a064
Date: Wed, 21 Aug 2019 09:23:49 +0000 [thread overview]
Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB04283@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1565595409-5768-1-git-send-email-nareddy@marvell.com>
Applied, thanks
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of
> nareddy@marvell.com
> Sent: Monday, August 12, 2019 3:37 PM
> To: dts@dpdk.org
> Cc: fmasood@marvell.com; avijay@marvell.com; Praneeth Reddy
> <nareddy@marvell.com>
> Subject: [dts] [PATCH] TestSuite_pmdrssreta.py: Modified rss ket size for
> cavium_a064
>
> From: Praneeth Reddy <nareddy@marvell.com>
>
> Required rss key size for cavium_a064 is 48
>
> Signed-off-by: Praneeth Reddy <nareddy@marvell.com>
> ---
> tests/TestSuite_pmdrssreta.py | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/tests/TestSuite_pmdrssreta.py b/tests/TestSuite_pmdrssreta.py
> index 9d29af8..fd1c181 100644
> --- a/tests/TestSuite_pmdrssreta.py
> +++ b/tests/TestSuite_pmdrssreta.py
> @@ -149,7 +149,7 @@ class TestPmdrssreta(TestCase):
> i = 0
> for tmp_reta_line in reta_lines:
> status = "false"
> - if(self.nic in ["cavium_a063"]):
> + if(self.nic in ["cavium_a063", "cavium_a064"]):
> # compute the hash result using simple XOR.
> hash_index_tmp = 0
> index_tmp = tmp_reta_line["RSS hash"].strip("0x") @@ -233,7
> +233,7 @@ class TestPmdrssreta(TestCase):
> self.verify("error" not in out, "Configuration of RSS hash failed:
> Invalid argument")
>
> # configure the reta with specific mappings.
> - if(self.nic in ["cavium_a063"]):
> + if(self.nic in ["cavium_a063", "cavium_a064"]):
> for i in range(64):
> reta_entries.insert(i, random.randint(0, queue - 1))
> self.dut.send_expect( @@ -259,7 +259,7 @@ class
> TestPmdrssreta(TestCase):
> self.dut.send_expect("quit", "# ", 30)
>
> def test_rss_key_size(self):
> - nic_rss_key_size = {"fortville_eagle": 52, "fortville_spirit": 52,
> "fortville_spirit_single": 52, "fortville_25g": 52, "niantic": 40, "e1000": 40,
> "redrockcanyou": 40, "atwood": 40, "boulderrapid": 40, "fortpark_TLV": 52,
> "hi1822": 40, "cavium_a063": 48}
> + nic_rss_key_size = {"fortville_eagle": 52, "fortville_spirit":
> + 52, "fortville_spirit_single": 52, "fortville_25g": 52, "niantic": 40,
> + "e1000": 40, "redrockcanyou": 40, "atwood": 40, "boulderrapid": 40,
> + "fortpark_TLV": 52, "hi1822": 40, "cavium_a063": 48, "cavium_a064":
> + 48}
> self.verify(self.nic in nic_rss_key_size.keys(), "Not supporte rss key
> on %s" % self.nic)
>
> dutPorts = self.dut.get_ports(self.nic)
> --
> 1.8.3.1
prev parent reply other threads:[~2019-08-21 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 7:36 nareddy
2019-08-21 9:23 ` 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=8CE3E05A3F976642AAB0F4675D0AD20E0BB04283@SHSMSX101.ccr.corp.intel.com \
--to=lijuan.tu@intel.com \
--cc=avijay@marvell.com \
--cc=dts@dpdk.org \
--cc=fmasood@marvell.com \
--cc=nareddy@marvell.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).